ns-spec-driven

Installation
SKILL.md

NextStage Spec-Driven

Delivery face for spec-driven journey: intake, clarify-strict, specify, (consistency / partition), tasks, execute, close.

Completeness before fidelity, both by construction. Clarify-Strict grill = Gate 0 only. Confirm gates 1–4 and brownfield Step 0.4 stay. Version Clarify-Strict ≠ per-issue enricher (ns-requirements-enricher). ns-project-manager stays decoupled.

Orchestratenot implement phase bodies inline. Read phase reference at delegation time. State on disk (docs/versions/, docs/context/, handoff files), not chat history.

Entry priority 2 (feature / version / SDD / multi-day / resume). Harness table: ../../ns-harness/references/code-skill-routing.md. Trigger phrases: references/entry-triggers.md. Bare quick fix, no SDD context → redirect ns-coder (priority 5) unless user explicitly invoked this skill.

Routing (read first)

Handoff Target
Small / quick inside SDD In-session ns-coder (cheap execute — MUST NOT spawn coder-agent; ../../ns-harness/references/subagent-dispatch.md)
Version + handoff references/execution-handoff.md + ../ns-coder/references/run-implementation.md + coder-agent (MUST when available — heavy)
Task file generation MUST spawn project agent task-writer-agent (exact name; adapter model) → references/task-generator.md. FORBIDDEN Task inherit / coder / generalPurpose (../../ns-harness/references/subagent-dispatch.md)
Bare quick fix, no SDD context Redirect ns-coder (priority 5) — cheap; in-session; MUST NOT spawn coder-agent
Installs
116
First Seen
Jul 25, 2026
ns-spec-driven — nextstage-brasil/skills