菜单
Mark a step as implemented in progress.yaml with notes and touched files. Use after completing each step instead of manual Edit calls.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Bootstrap phase context for Builder. Provides current phase, next step, and full phase file contents.
Bootstrap phase context for Overseer. Provides phase under review with full file contents and card metadata.
Approve a phase — sets status to complete, marks all steps reviewed, updates linked card. Use when declaring a phase green.
Create a phase directory with all required files in one call. Use instead of separate mkdir + Write calls when creating a new phase.
Kick a phase back to building — sets status and adds new step entries to progress.yaml. Use when requesting fixes from Builder.
Set the status field in a phase's progress.yaml. Use instead of manual Edit calls when transitioning phase status.
| name | mark-step-done |
| description | Mark a step as implemented in progress.yaml with notes and touched files. Use after completing each step instead of manual Edit calls. |
| user-invocable | false |
Updates a step entry in progress.yaml to set implemented: true, and optionally sets notes and touched file list. Handles both touched and files field names.
python3 ${CLAUDE_PLUGIN_ROOT}/skills/mark-step-done/mark-step-done.py <phase-dir> <step-id> [--notes "..."] [--files file1 file2 ...]
phase-dir: Path to the phase directorystep-id: The step ID to mark done (e.g., S001 or 1)--notes: Optional description of what was done--files: Optional list of files touched by this step# Simple completion
python3 ${CLAUDE_PLUGIN_ROOT}/skills/mark-step-done/mark-step-done.py .ushabti/phases/0005-my-phase S001 --notes "Protocol defined" --files src/protocol.ts src/types.ts
# Without notes or files
python3 ${CLAUDE_PLUGIN_ROOT}/skills/mark-step-done/mark-step-done.py .ushabti/phases/0005-my-phase S002
This replaces the manual read-edit-write cycle on progress.yaml after each step.