← ClaudeAtlas

wiki-speclisted

Spec history management. Before authoring a new spec (PRD / design / RFC / ADR / task-spec / decisions), surface related prior specs from the kata wiki so the author can declare relationships (supersedes / refines / extends / parallel / contradicts). v1.13 Phase 0+2: scan + advisory + enforcement. Phase 3 auto-propagates. Cross-source authoring is served by wiki-import (bulk human ingest) or v1.12 cross-wiki federation.
litianyi-007/kata · ★ 0 · AI & Automation · score 73
Install: claude install-skill litianyi-007/kata
# wiki-spec Spec-aware authoring helper. The problem this solves: SDD / superpowers-style flows generate many specs over time. New specs frequently overlap, refine, or override older specs, but most tools have no mechanism to make the new-spec author "answer for" the older specs. Result: a corpus that drifts from a coherent decision record into a pile of disconnected pages. `wiki-spec` closes this gap by scanning the wiki at the moment a new spec is about to be ingested, surfacing prior specs that overlap on tags / title / explicit wikilinks, and (in Phase 2+) enforcing that the new spec declare relationships before ingest succeeds. ## Phase 0+2 — advisory scan + enforcement (current) Scope: - Scan kata-managed wiki pages whose frontmatter `type` is in `spec_types` - Score and rank candidates by relevance (title overlap, tag overlap, wikilink reference, hub centrality, type match) - **Phase 2 enforcement (v2.4.0+)**: with `--enforce` (or `spec_authoring.enforce_relationship_declaration: true` in SCHEMA.md), the script rejects ingest when any candidate scored at-or-above `enforcement_score_threshold` is not addressed in the new spec's `spec_relationships:` block. Exit codes: 0 = accept, 2 = reject (strict), 1 = reject (confirm — agent should prompt for resolution). - Kata-internal only by design — no reaching outside `{wiki_path}/`. ## Cross-source authoring (NOT this skill) Two valid paths for legacy / cross-project spec corpora: 1. **`wiki-import`** — huma