Living Spec Consolidator

Maintain docs/specs/ as current functional truth of product.

Session boot

See ../../ns-harness/references/session-boot.md and ../../ns-harness/references/artifact-layout.md.

Modes

Appearance if invoker pass mode appearance (or equivalent: guide/prototype path + behavioral delta, no review verdict). Ad-hoc if mode ad-hoc (or equivalent: no {version_san}, task description + approved diff). Else Version.

When invoked

• Version closure post Code Review: Approved — Version
• Ad-hoc coding, review Approved, docs/specs/ exists — Ad-hoc
• Prototype create/evolve or normative visual guides documenting behavioral UX — Appearance
• Not Version/Ad-hoc before Code Review: Approved

Prerequisites

Version mode

• Resolved requirements.md — sdd/ first, else legacy version root (artifact-layout.md Legacy path resolution)
• Invoker reports Code Review: Approved — no code-review-report.md required
• Resolved execution-handoff.md — sdd/ first, else legacy version root (tasks completed)

Ad-hoc mode

• docs/specs/ already exists (not create tree from scratch)
• Invoker reports Code Review: Approved
• {task_description} + approved working-tree diff (behavioral change)
• Skip (no writes) if diff non-behavioral: cosmetic, rename-only, pure refactor with no API/schema/UX/domain behavior change — report skipped

Appearance mode

• Input: path to appearance guide and/or prototype/ surface + short behavioral delta (what users can do / see changed or captured)
• May create docs/specs/ + INDEX.md if missing
• SHALL only for product-visible behavior (flows, fields, states, permissions cues)
• Never paste Element | How it should appear tables into domain specs — link guide instead
• Skip pure chrome polish (spacing, color tweak, font swap, no behavior change) — report reason
• No Code Review / Approved requirement

Workflow

Shared steps 1–4 all modes. Changelog label differs by mode.

1. Identify affected domains

Map features to canonical domains (examples):

docs/specs/agent-architecture.md is the living ADR (ns-multi-agent-architect). Not a domain spec. Do not treat as {domain}.md.

Naming: English, kebab-case, singular (user-profile.md). Multi-domain features update multiple specs.

Ad-hoc: map from {task_description} + diff only — no invent unrelated domains.

Appearance: map from behavioral delta + guide/prototype scope only; add domain links to appearance docs under Related / references when useful.

2. Per domain

If docs/specs/{domain}.md missing: create from references/domain-spec.template.md

If exists: read entirely; append or update — never blind overwrite

Per relevant feature:

• Add or update ### Requirement: blocks (SHALL + scenarios)
• Update ## Data model + ## Endpoints when schema/API changed (Version/Ad-hoc)
• Appearance: prefer UX/behavior requirements; no invent APIs/schemas not evidenced
• Append ## Changelog entry:

- Version: {version_san} — {ISO date}: {summary} - Ad-hoc: adhoc-YYYY-MM-DD — {ISO date}: {summary} (summary from task + diff) - Appearance: appearance-YYYY-MM-DD — {ISO date}: {summary}

3. Update INDEX.md

Create or update docs/specs/INDEX.md:

# Domain specs — {product_name}

| Domain | File                 | Last updated | Versions      |
| ------ | -------------------- | ------------ | ------------- |
| auth   | `docs/specs/auth.md` | {date}       | {version_san or adhoc-YYYY-MM-DD or appearance-YYYY-MM-DD} |

4. Consolidation report

Emit short report for handoff:

## Living specs updated
| Domain | Action | File |
...
Mode: {version|ad-hoc|appearance}
Requirements added: N
Requirements updated: N
New specs: N

If skipped (non-behavioral, polish-only, or Ad-hoc missing docs/specs/):

## Living specs skipped
Reason: {missing docs/specs/|non-behavioral diff|chrome polish only}

Critical rules

• English for spec content
• Requirements use verifiable SHALL language
• Read before write on existing specs
• Planning orchestrator read INDEX.md before new version requirements
• Ad-hoc must not create version artifacts under docs/versions/
• Ad-hoc must not invent {version_san}
• Appearance must not paste normative Element|How tables into specs
• Appearance must not require Code Review Approved
• Do not overwrite docs/specs/agent-architecture.md (ns-multi-agent-architect living ADR). agent.md is behavior only

Related skills

• ns-spec-driven — reads living specs when planning (references/requirements-generator.md)
• ns-reviewer — prerequisite Code Review: Approved for Version/Ad-hoc
• ns-coder — may invoke ad-hoc after Approved
• ns-proto-creator / ns-proto-visual-guide — may invoke appearance mode