sdlc-spec

Facilitate decision interviews and write approved specification documents for delivery initiatives.

Updated Sep 11, 2026
One-click install
npx skills add https://github.com/zhixuan312/zz-stack --skill sdlc-spec-zhixuan312
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdlc-spec
Source: https://github.com/zhixuan312/zz-stack/tree/main/catalog/sdlc/sdlc-flow/skills/sdlc-spec
Command: npx skills add https://github.com/zhixuan312/zz-stack --skill sdlc-spec-zhixuan312

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a rough idea into a specification that people actually agree on is hard: decisions get made implicitly, requirements stay vague, and documents get written that nobody approved. This Skill runs the whole conversation — opening the option space with the person, closing it to confirmed decisions, and writing the agreement as a formal spec.md that a platform gate can enforce. ## Core Features & Use Cases - Structured brainstorm interview: One decision at a time, with mechanical questions dispatched to investigation workers and genuine trade-offs presented to the person with options and a recommendation. - Eight-component specification writer: Produces spec.md with the canonical sections (Context, Problem, Goals & Requirements, Alternatives, Approach Method & Structure, Verification Plan, Risks & Mitigations, Stakeholders & Work) via a skeleton-then-enrich writing discipline. - Deliverable contract proposal: Drafts kind, audience, disposition, artifacts, and acceptance criteria with explicit verification methods (command, agent-review, or human) for the person to confirm. - Use Case: After an exploration phase establishes what is true about a system, use this Skill to interview the stakeholder on scope and priorities, then write an auditable spec that downstream planning and audit stages can consume. ## Quick Start Ask the agent to run the sdlc-spec stage for your initiative to interview you on the open decisions and write the confirmed agreement into spec.md for approval.

Frequently Asked Questions about sdlc-spec

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a software specification from stakeholder decisions?▼

Run a structured interview that resolves one decision per message, record each answer with its rationale, then scaffold the spec with all required headings and enrich each section individually. This Skill writes the result to spec.md through document_write so it can be approved and audited.

What sections should a technical specification document contain?▼

This flow requires eight components: Context, Problem, Goals & Requirements, Alternatives, Approach Method & Structure, Verification Plan, Risks & Mitigations, and Stakeholders & Work. A component that does not apply keeps its heading and states why rather than being omitted.

Can the spec-writing stage be delegated to a subagent?▼

No. Brainstorm and spec are one conversation with the person in the room, so this stage is never dispatched to a worker. Delegating the deciding produces a confident document nobody agreed to, which fails the approval gate downstream.

Why does the platform refuse to approve my spec document?▼

Approval is refused when any of the eight canonical ## headings is missing, since flow.json declares them for spec.md. Write all eight headings in the skeleton phase even if a section only states that it does not apply.

When should I run sdlc-explore before writing a spec?▼

Run sdlc-explore first when nothing has been established about the system or the stakeholder cannot name a destination for the spec. Interviewing without grounding produces a document about the agent's own assumptions.