From cycles
Generate a technical specification from a roadmap milestone. Reads the roadmap, design doc, and existing specs to produce a detailed spec for the next milestone.
npx claudepluginhub karimstekelenburg/k3m-marketplace --plugin cycles/specStarts spec-driven development: asks clarifying questions on objectives, features, tech stack, and boundaries; generates structured SPEC.md covering six core areas; confirms before proceeding.
/specAuthors structured NLSpec from natural language description using multi-AI research, with adversarial completeness validation, scoring, and saved spec file.
/specGenerates complete feature specifications from a feature name or rough idea, spanning requirements to implementation plan.
/specGenerates spec-driven development docs from a feature description: requirements.md (EARS user stories), design.md (Mermaid diagrams, TypeScript interfaces), tasks.md (implementation plan).
/specGenerates detailed feature specs via 3-phase interactive dialogue from minimal input, producing requirements.md (EARS), design.md (diagrams/TS), and tasks.md.
/specGenerates spec docs from feature description: requirements.md (EARS notation), design.md (Mermaid diagrams, TS interfaces), tasks.md (implementation plan).
Generate a technical specification for a roadmap milestone.
The user provides a milestone identifier (e.g., "v0.2", "Canvas Viewport") or asks for "the next spec."
Detect backend and source it:
source "$CLAUDE_PLUGIN_ROOT/scripts/detect-backend.sh" && source "$K3M_BACKEND_SCRIPT"
Read context:
k3m_read_roadmap — find the target milestonedocs/DESIGN.md — architectural context (always on filesystem)docs/specs/ (fs) or marked comments (github)src/ — current implementationGenerate the spec with this structure:
# v{X.Y.0} — {Milestone Name}: Technical Spec
> **Status:** Draft · **Date:** {today}
> **Depends on:** {previous milestone}
> **Estimated effort:** {from roadmap}
---
## 1. Goal
## 2. Design decisions
## 3. Architecture
### 3.1 Class structure
### 3.2 File layout
## 4. Data model
## 5. Public API
## 6. Internal implementation
## 7. Event flow
## 8. Acceptance criteria
## 9. Playground update
## 10. Migration / breaking changes
## 11. Open questions
Write the spec:
docs/specs/v{X.Y}-{kebab-case-name}.md<!-- k3m:spec -->) on the milestone issueUpdate state:
specced label to the issueReport the file path/location and a brief summary.