specsafe

Create a system architecture document with design decisions, patterns, and component structure. Requires a PRD.

Facilitate structured brainstorming sessions for product, feature, workflow, or system ideas. The entry point for ambiguous ideas before they become principles or briefs.

Create a product brief — the executive summary of what you're building, who it's for, and why it matters. Use before creating a PRD.

TDD implementation using red-green-refactor cycle. Unskips tests one at a time and writes minimum code to pass.

Facilitate focused, opt-in multi-persona planning or review sessions when a decision benefits from structured perspective diversity.

Create a Product Requirements Document from a product brief. Defines user journeys, functional requirements, non-functional requirements, and scope.

Convert brainstorming output and early product thinking into a stable set of decision-making principles, non-goals, and quality priorities. Use before creating a product brief.

Final gate between planning and development. Validates that all planning artifacts are coherent, aligned, and sufficient to safely begin implementation as spec slices.

Create custom SpecSafe skills that integrate into the TDD pipeline. Build your own workflow steps, quality gates, or utility skills.

Generate test files from spec scenarios. Transitions spec from SPEC to TEST stage. All tests start skipped.

Create UX design principles, design system foundations, and accessibility guidelines. Best used after PRD creation.

Generate a project context document that captures coding conventions, patterns, tech stack, and critical rules for AI tools. Helps AI agents write consistent code.

Archive an obsolete or abandoned spec with a reason. Moves spec out of active/completed into archive.

Human approval gate for completing a spec. Moves spec from QA to COMPLETE stage after explicit approval.

Validate project health. Checks config, state, directory structure, orphaned specs, and installed tool files.

Pre-spec exploration and research mode. Use before creating a spec when the problem space needs investigation.

Initialize a new SpecSafe project in the current directory. Creates spec directories, config, and PROJECT_STATE.md.

Create a new spec with a unique ID, initial requirements, and scope. Use when starting a new feature or change.

Full QA validation with report generation and GO/NO-GO recommendation. Validates all requirements and scenarios.

Refine an existing spec with detailed requirements, acceptance criteria, scenarios, and implementation plan.

Show project dashboard with spec counts by stage, active specs, completed specs, and metrics.

Run tests and validate implementation against spec. Loops back on failure. Moves spec from CODE to QA stage.

Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.

Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.

Archive multiple completed changes at once. Use when archiving several parallel changes.

Continue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue their workflow.

Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.

Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.

Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.

Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.