菜单
Verification phase for {PROJECT} — unit and integration tests, isolation/access checks, and an end-to-end pass over the critical path for a completed slice. Called by project-orchestrator after implementation; also used directly when the user says "verify {PROJECT}'s X module" or "test this."
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Log a vault change (note created/edited/deleted) to a running daily changelog note. After any write to the vault, ask the user "should this be logged?" and run this skill on confirmation. Also runs directly when the user says /changelog.
Update a project's README and the relevant vault notes (overview / module map) after a meaningful code change — new feature, new file, new module, or an architectural decision. Should trigger on its own once a coding task is finished, without the user having to ask — skip it for trivial (typo/formatting) changes. Also runs manually when the user says "update the docs" or "document this."
Update "where we left off" tracking for {PROJECT} when a milestone or unit of work closes. Updates Status.md (active milestone + next concrete action) and Milestone_Log.md (chronological record); touches Goal.md/Decisions.md if needed. Called by project-orchestrator at the end of every milestone; also used directly when the user says "log this milestone" or "update status."
Design phase for {PROJECT} — data model, module boundaries, API contract, access control, and any multi-tenancy/security design, before code is written. Called by project-orchestrator before implementation; also used directly when the user says "design {PROJECT}'s X module."
Implementation phase for {PROJECT} — builds the actual code for a module or vertical slice against an existing design. Called by project-orchestrator once a design exists; also used directly when the user says "implement {PROJECT}'s X module."
Main orchestrator for building {PROJECT}. Tracks cross-session continuity, reads "where we left off," routes to the correct phase sub-skill, and runs autonomously. Use when the user says "continue {PROJECT}," "work on {PROJECT}," "{PROJECT} where did we leave off," or /project-orchestrator. This is for the BUILD side of {PROJECT} — not for unrelated day-to-day tasks about it.
| name | project-verify |
| description | Verification phase for {PROJECT} — unit and integration tests, isolation/access checks, and an end-to-end pass over the critical path for a completed slice. Called by project-orchestrator after implementation; also used directly when the user says "verify {PROJECT}'s X module" or "test this." |
Confirms a change actually does what it claims — by exercising the affected flow, not just by trusting that tests/type-checks pass (see 08 — Project Development Lifecycle).
A diff that only touches tests or documentation, with no runtime surface to exercise, doesn't need the end-to-end pass — say so explicitly rather than fabricating a verification step that wouldn't observe anything real.
Report exactly what failed and why, and hand back to project-implement (or project-design, if the failure reveals a design gap) rather than silently patching around a symptom.
