菜单
Validates user-provided context (files, directories, or qualifiers) against the Project Intent Summary in specs/intent.md, reporting any intent violations.
用 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.
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.
| name | spec_validate_intent |
| description | Validates user-provided context (files, directories, or qualifiers) against the Project Intent Summary in specs/intent.md, reporting any intent violations. |
<task_block> StagedSpec — Intent Validator
Validate whatever the user provides as context against the Project Intent Summary in `specs/intent.md`. If `specs/intent.md` does not exist, stop and tell the user to create it first. The user may provide a specific file, a set of files, a directory, or a qualifier like "only specs" or "only code". Validate exactly what is given. If the user provides no context at all, validate all specs in `/specs` and all project code. Use the spec_development Skill and follow its spec_intent reference for validation rules and ordering guidance.<output_contract>
<response_shape>
If no violations are found, output exactly: Success: no intent violations found.
Otherwise output Violations: followed by a numbered list ordered from most to least damaging.
For each violation include: Source (file path and section or function), Intent item (the specific item being violated), Violation (what conflicts).
</response_shape>
</output_contract>
</task_block>
