Development Skills (Phase 2)

Phase 2 skills drive the spec-to-delivery lifecycle. Each spec moves through defined stages: NEW, SPEC, TEST, CODE, QA, and COMPLETE. These skills advance specs through that pipeline.

specsafe-init

Initialize a new SpecSafe project. Creates the specs/ directory structure, PROJECT_STATE.md, and configuration files.

Usage:

specsafe init <project-name>

When to use: Once per project, at setup time.

Key output: specs/ directory with active/ and complete/ subdirectories, PROJECT_STATE.md, and config.

specsafe-new

Create a new spec with a unique ID. Each spec gets a timestamped identifier and starts in the NEW stage.

Slash command: /specsafe-new

Usage:

/specsafe-new "user authentication with OAuth2"

Key output: A new spec file at specs/active/SPEC-YYYYMMDD-NNN.md in the NEW stage.

specsafe-explore

Enter a pre-spec exploration and research mode. Use this when you need to investigate a problem space, read existing code, or clarify requirements before committing to a spec.

Slash command: /specsafe-explore

When to use: When you are not yet sure what the spec should contain. Explore first, then create.

Key output: Notes and findings that inform the spec.

/specsafe-explore "how does the current auth system work?"

specsafe-spec

Refine a spec with detailed requirements, acceptance criteria, and scenarios. This moves the spec from a rough description to a precise, testable definition.

Slash command: /specsafe-spec

Usage:

/specsafe-spec SPEC-20260406-001

When to use: After creating a spec with /specsafe-new. Fleshes out requirements and acceptance criteria.

Key output: Updated spec file with detailed requirements, acceptance criteria, and edge case scenarios.

specsafe-test

Generate test files from a spec. All tests start skipped. This is deliberate: tests define the target behavior before any code exists.

Slash command: /specsafe-test

Usage:

/specsafe-test SPEC-20260406-001

When to use: After the spec is refined. Moves the spec from SPEC to TEST stage.

Key output: Test files with all tests initially skipped. The spec advances to TEST stage.

specsafe-code

TDD implementation. Unskip one test at a time, write the minimal code to make it pass, refactor, then repeat. This enforces the red-green-refactor cycle.

Slash command: /specsafe-code

Usage:

/specsafe-code SPEC-20260406-001

When to use: After tests are generated. Moves the spec from TEST to CODE stage.

Key output: Implementation code that passes all unskipped tests. The spec advances to CODE stage.

specsafe-verify

Run tests and validate the implementation against the spec. If all tests pass and the implementation matches the spec, the spec advances from CODE to QA.

Slash command: /specsafe-verify

Usage:

/specsafe-verify SPEC-20260406-001

When to use: After implementation is complete. Confirms readiness for QA review.

Key output: Test results and validation report. Advances to QA stage if passing.

specsafe-qa

Full QA validation with a structured report. Produces a GO or NO-GO recommendation based on test coverage, spec compliance, and edge case handling.

Slash command: /specsafe-qa

Usage:

/specsafe-qa SPEC-20260406-001

When to use: After verification passes. This is the quality gate before completion.

Key output: QA report with GO/NO-GO recommendation.

specsafe-complete

Human approval gate. This is where a human reviews the QA report and decides to accept or reject the spec. Moves the spec from QA to COMPLETE.

Slash command: /specsafe-complete

Usage:

/specsafe-complete SPEC-20260406-001

When to use: After QA passes with a GO recommendation. Requires human sign-off.

Key output: Spec moves to COMPLETE stage and is archived.

specsafe-status

Project dashboard showing spec counts by stage. Gives you a quick overview of where everything stands.

Slash command: /specsafe-status

Usage:

/specsafe-status

Key output: Summary table of specs grouped by stage (NEW, SPEC, TEST, CODE, QA, COMPLETE).

specsafe-doctor

Validate project health and configuration. Checks for common issues like missing config, orphaned specs, or inconsistent state.

Slash command: /specsafe-doctor

Usage:

/specsafe-doctor

Key output: Health report with warnings and errors, if any.

specsafe-archive

Archive obsolete or abandoned specs. Archived specs are preserved for historical reference but removed from active tracking.

Slash command: /specsafe-archive

Usage:

/specsafe-archive SPEC-20260406-001

When to use: When a spec is no longer relevant. Prefer archiving over deleting.

Key output: Spec moved to archive with a timestamp.