staged-spec

StagedSpec: Guides iterative development and assessment of project specs in /specs with an architecture index, staged specs, implemented status tracking, and feature documentation. Use when creating, refining, or checking specs, architecture.md, stage files, features.md, security.md, or testing.md.

Implements a spec completely end-to-end including all code, tests, and verifications. Follows a strict read-understand-implement-verify workflow.

Bootstraps the StagedSpec framework in a new project: creates the /specs folder, guardrail documents (intent.md, security.md, testing.md), architecture.md index, optional features.md for existing code, and optional initial stage specs. Use when a project has no /specs folder or is missing guardrail documents.

Audits specs marked as Implemented in specs/architecture.md against the actual codebase. Verifies feature implementation, tests, and verification items end-to-end, reporting gaps between specified and built behavior.

Derives a Project Intent Summary from an existing /specs folder that has stages but no intent.md. Analyzes all documents in /specs and produces specs/intent.md, then adds an intent summary paragraph to specs/architecture.md. Use when a project already has specs but is missing intent.md — for new projects, use spec_init instead.

Reviews a single stage spec for implementation readiness. Uses the spec_development skill's single_stage_assessment reference for detailed assessment guidance. Produces one direct assessment from the current agent.

Updates specs/features.md to reflect actual implemented behavior by inspecting the current codebase end-to-end.

Validates user-provided context (files, directories, or qualifiers) against the Project Intent Summary in specs/intent.md, reporting any intent violations.