菜单
Use when you have a written implementation plan to execute in a separate session with review checkpoints
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Use when executing implementation plans with independent tasks in the current session
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Use when you have a spec or requirements for a multi-step task, before touching code
Use after implementation is verified and before merge — consolidates multiple spec iterations into a single final-state report, marks related specs, and records key lessons
Use when you want to evolve your own capabilities — create new tools to avoid repeating patterns, add hooks to improve your own behavior, build skills to accumulate domain knowledge, or override built-in tools to adapt to project needs. This is your self-iteration interface.
| name | compose:execute |
| hidden | true |
| description | Use when you have a written implementation plan to execute in a separate session with review checkpoints |
Load plan, review critically, execute all tasks, report when complete.
Announce at start: "I'm using the compose:execute skill to implement this plan."
Note: Compose works much better with access to subagents. If subagents are available, use compose:subagent instead of this skill for significantly higher quality.
task tool and proceedFor each task:
After all tasks complete and verified:
STOP executing immediately when:
Use compose:ask to present the blocker and options rather than describing it in free text. If no user is available, resolve the blocker with your best judgment and continue.
Return to Review (Step 1) when:
Don't force through blockers - stop and ask.
Required workflow skills: