Overview
/silver:spec exists for work where the requirements need to be made explicit before GSD planning. It guides a product-style elicitation session, records assumptions, writes the canonical spec artifacts, and runs artifact review before downstream planning consumes the result.
It does not implement code. Its job is to turn a fuzzy or formal product request into traceable planning inputs.
Core value: SB prevents premature implementation by requiring a spec with acceptance criteria, out-of-scope boundaries, assumptions, and source-artifact references before GSD starts planning.
When to Use
- The feature has ambiguous scope or multiple user stories.
- You need acceptance criteria before planning or implementation.
- You are augmenting an existing
.planning/SPEC.mdand need a new spec version. - The work depends on assumptions that should be visible to reviewers and implementers.
Outputs
| Artifact | Purpose |
|---|---|
| .planning/SPEC.md | Canonical feature spec with overview, user stories, UX flows, acceptance criteria, assumptions, open questions, out-of-scope boundaries, source artifacts, and spec version. |
| .planning/REQUIREMENTS.md | Derived REQ/NFR list tied back to acceptance criteria and non-functional concerns. |
| .planning/DESIGN.md | Conditional output when a design artifact or Figma URL is part of the spec context. |
Workflow Steps
- Mode detection: detect greenfield vs augment mode by checking whether
.planning/SPEC.mdalready exists. - Context gathering: collect feature name, description, and optional JIRA, Figma, Google Doc, or presentation links.
- Spec scaffold: invoke
product-management:write-specwhen available to establish a formal PM spec structure. - Socratic elicitation: ask structured questions across problem, user goal, scope boundary, user stories, acceptance criteria, edge cases, error states, data model, and open questions.
- Assumption consolidation: resolve, accept, or tag every assumption before writing the spec.
- Artifact injection: incorporate available source artifacts and record inaccessible sources explicitly.
- Write and review artifacts: write SPEC.md, derive REQUIREMENTS.md, optionally write DESIGN.md, then run artifact review to two consecutive clean passes.
Non-Skippable Gates
The core spec contract cannot be skipped:
- Socratic elicitation minimum coverage
- Assumption consolidation
- Writing
.planning/SPEC.md - SPEC artifact review
- REQUIREMENTS artifact review
- DESIGN artifact review when DESIGN.md is produced
GSD Handoff
After /silver:spec completes, use /silver:validate when plans already exist or proceed into the appropriate /silver feature path. GSD planning consumes the spec and requirements as upstream constraints; SB hooks later maintain PR traceability and UAT freshness against the spec version.
/silver:spec Add scheduled report exports for admins
/silver:validate
/silver Build the scheduled report export feature