plan-one-shot
Installation
SKILL.md
Plan One Shot
Replicate Antigravity plan-mode behavior using three artifacts and strict review gates.
Hard Rules
- Before approval: plan only. No code edits, no mutating commands, no commits.
- Always produce or update these artifacts together:
.exspecso/<plan-name>/task.md.exspecso/<plan-name>/implementation_plan.md.exspecso/<plan-name>/walkthrough.md(stub only during planning)
- Match plan depth to scope.
- Block execution until user says exactly:
Execute Plan. - Do not skip artifact generation even for short tasks.
- After approval: execute strictly in
task.mdorder and update statuses continuously. - For existing projects, preserve architecture, naming, folder layout, and dependency choices unless the user asks for a change.
- Prefer minimal diff; do not introduce new abstractions/libraries unless justified by at least two concrete reuse points or a clear blocker.
- First call in a new conversation defaults to new planning. Do not infer an active plan from
.exspecso/history. - Only resume prior plan artifacts when the user explicitly asks to continue/resume an existing plan.