executing-plans
/executing-plans
Use when implementing an approved written plan with dependent tasks in the current session. Do NOT use when the plan is missing, unapproved, or naturally parallel.
- Author
- tsergeytovarov ↗
- Repository
- ai-settings ↗
- Licence
- MIT
- Last repository change
- 14.10.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 14.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use when implementing an approved written plan with dependent tasks in the current session. Do NOT use when the plan is missing, unapproved, or naturally parallel.
Original author description
Use when implementing an approved written plan with dependent tasks in the current session. Do NOT use when the plan is missing, unapproved, or naturally parallel.
How it works
- Process
- Stop and Ask
SKILL.md preview
--- name: executing-plans version: 6.2.0 category: workflow description: Use when implementing an approved written plan with dependent tasks in the current session. Do NOT use when the plan is missing, unapproved, or naturally parallel. --- # Executing Plans Execute the plan in the current agent by default. ## Process 1. Read the plan and applicable project instructions. 2. Confirm the workspace and existing user changes are safe. 3. Flag only gaps that block or materially change the outcome. 4. Track tasks by useful deliverable, not every command. 5. For each task, implement the scoped outcome and run its risk-appropriate verification. 6. Update the plan or canonical backlog when reality changes. 7. Review the complete diff once at the end. Read `../using-superpowers/references/risk-policy.md`. Do not switch to subagent-driven development merely because subagents exist. Delegate only when the user requests it or tasks are independent enough to benefit from parallel work. ## Stop and Ask Stop when authority is missing, a destructive action is newly required, a critical requirement is ambiguous, or repeated evidence invalidates the plan. Ordinary implementation details are resolved from the codebase. When implementation is verified, use `superpowers:finishing-a-development-branch` only if an integration decision is actually needed.
Files in this package (2)
- CHANGELOG.md 1 KB
- SKILL.md 1 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · tsergeytovarov/ai-settings | 90 | MIT |
| nikospavlopoulos/devops-mutant-powers | 100 | MIT |
| arklab/ark.tools | 100 | MIT |
| arklab/ark.tools | 100 | MIT |
| ongtungduong/legion | 100 | MIT |
| osmontero/opencode-skills | 100 | MIT |
| GanyuanRan/Aegis | 100 | MIT |
| seaworld008/commonly-used-high-value-skills | 100 | MIT |
| FrancoStino/opencode-skills-collection | 100 | MIT |
Database snapshot: 13.11.2026 · package version 6916bd159faa (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100assemble
Use when executing implementation plans with independent tasks in the current session - 100subagent-driven-development
Use when executing implementation plans with independent tasks in the current session - 90sr-executing-plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints