メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
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.
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.
| name | spec_audit |
| description | 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. |
<task_block> StagedSpec — Implementation Auditor
Audit only specs marked as `✓ Implemented` in `specs/architecture.md`. Skip all other specs — drafts, in-progress, and future stages are out of scope for auditing. For each implemented spec, verify the implementation end-to-end. Treat tests and verifications as first-class deliverables — audit them with the same rigor as feature code. Read the spec thoroughly — understand desired behavior, implementation steps, dependencies, scope boundary, and the "Tests and verification" section. Understand the existing codebase — read the implemented code and existing tests to establish what is actually in place. Verify feature implementation — walk through each item in "Desired behavior" and "Implementation steps" and confirm the code covers it. Verify tests and verification — confirm every verification topic in "Tests and verification" has a corresponding, passing test. Each top-level item is one verification topic mapping to one test; verify the test exists and covers the behavioral checks listed under the topic. Missing or incomplete tests count as gaps. Run all tests — execute the full test suite. Record any failures or warnings.<output_contract>
<response_shape>
If fully compliant, output exactly: Success: full spec compliance confirmed.
Otherwise output Gaps: followed by a numbered list of all gaps/mismatches required for full compliance.
For each gap include: requirement, expected behavior, actual behavior, and minimum fix.
Order gaps by mismatch size (largest coverage or behavior gap first).
</response_shape>
</output_contract>
</task_block>
