spec-retro
25Command
Run a retrospective on a completed spec to capture lessons learned.
Command
Run a retrospective on a completed spec to capture lessons learned.
Command
Show status and progress of current spec.
Command
Regenerate tasks from updated spec requirements and design.
Command
Validate spec completeness and consistency.
Command
Run post-deployment smoke tests against a live environment.
Command
Start a new spec-driven development workflow for a feature.
Command
Extract and formalize domain terminology into a canonical glossary, flagging ambiguities and proposing precise terms. Saves to UBIQUITOUSLANGUAGE.md.
Command
Zoom out and provide a high-level map of modules and callers for unfamiliar code.
Agent
The plugin uses 11 specialized agents, each optimized for a specific phase of the workflow. You don't invoke agents directly — they are automatically dispatched by commands like /spec, /spec-brainstorm, and the post-implementation commands.
Command
Commands use / prefix in Claude Code and $ prefix in Codex. Execution scripts (spec-loop.sh, spec-exec.sh, etc.) are run from the terminal in your project root.
Skill Claude CodeCodex
This skill should be used when the user asks to "create a spec", "write requirements", "design a feature", "plan implementation", "use EARS notation", "create user stories", "break down tasks", "write a PRD", "technical specification", or mentions "spec-driven development", "feature spec", "requirements phase"…
Instructions file CodexOpenCode
TypeScript MCP server template with tools, resources, prompts, and session configuration.