Executing Plans
Quick Start
- Prepare - Read entire plan, verify understanding, check dependencies
- Execute Task - Read -> Navigate -> Implement -> Verify -> Complete
- Track Progress - Update status after each task, report blockers immediately
- Pass Quality Gates - Validate after task, after phase, before completion
- Handle Deviations - Document changes, get approval for scope changes
Features
| Feature |
Description |
Guide |
| Preparation Phase |
Understand before starting |
Read plan, verify deps, clarify questions |
| Task Execution |
Systematic per-task flow |
Read, navigate, implement, verify, complete |
| Progress Tracking |
Real-time status updates |
Completed X, In Progress Y, Remaining Z |
| Quality Gates |
Validation checkpoints |
Per-task, per-phase, pre-completion |
| Blocker Resolution |
Unblock systematically |
Document, assess, attempt, escalate, workaround |
| Deviation Handling |
Adapt to discoveries |
Document, assess scope/timeline, get approval |
Common Patterns
# Task Execution Checklist
BEFORE STARTING:
[ ] Read task description completely
[ ] Understand acceptance criteria
[ ] Check dependencies completed
[ ] No blockers present
DURING IMPLEMENTATION:
[ ] Navigate to specified files
[ ] Understand existing code context
[ ] Implement changes incrementally
[ ] Write tests alongside code
AFTER COMPLETION:
[ ] All acceptance criteria met
[ ] Tests pass locally
[ ] No lint/type errors
[ ] Task marked complete
# Quality Gates
AFTER EACH TASK:
npm run lint && npm run typecheck && npm test -- --related
AFTER EACH PHASE:
npm run lint && npm run typecheck && npm test && npm run build
BEFORE COMPLETION:
npm run lint && npm run typecheck && npm test --coverage && npm run build
# Progress Report Template
## Status: [Date Time]
### Summary
- Completed: [N] tasks
- In Progress: [Task name]
- Remaining: [M] tasks
- Blockers: [None | Description]
### Current Task
**[Task Name]:** [Description]
- Started: [Time]
- Progress: ~60%
- Expected completion: [Time]
### ETA
On track for [date] | Delayed by [reason]
# Blocker Resolution Flow
BLOCKER DETECTED
|
1. DOCUMENT immediately
- What is blocked?
- Why is it blocked?
|
2. ASSESS impact
- Critical path affected?
- Time sensitive?
|
3. ATTEMPT resolution (15-30 min)
- Quick research
- Alternative approach
|
+-> RESOLVED -> Continue
|
4. ESCALATE if not resolved
- Report with: issue, attempts, ask
|
5. WORK AROUND while waiting
- Move to non-blocked tasks
Best Practices
| Do |
Avoid |
| Read entire plan before starting |
Skipping preparation phase |
| Verify understanding of each task |
Assuming task requirements |
| Execute tasks in sequence (unless parallel) |
Ignoring quality gates |
| Validate after each task completion |
Hiding blockers or delays |
| Report blockers immediately |
Deviating without documenting |
| Document deviations as they occur |
Rushing quality for speed |
| Complete fully before marking done |
Leaving tasks partially done |
| Ask questions early |
Skipping testing steps |
Related Skills
writing-plans - Create plans to executeverifying-before-completion - Quality gate checkliststhinking-sequentially - Track execution progresssolving-problems - Resolve blockers systematically
Converted and distributed by TomeVault — claim your Tome and manage your conversions.
1---2name: executing-plans-53description: AI agent follows implementation plans systematically with progress tracking, quality gates, and blocker resolution. Use when implementing features, following plans, or executing tasks. Use when this capability is needed.4---56# Executing Plans78## Quick Start9101. **Prepare** - Read entire plan, verify understanding, check dependencies112. **Execute Task** - Read -> Navigate -> Implement -> Verify -> Complete123. **Track Progress** - Update status after each task, report blockers immediately134. **Pass Quality Gates** - Validate after task, after phase, before completion145. **Handle Deviations** - Document changes, get approval for scope changes1516## Features1718| Feature | Description | Guide |19|---------|-------------|-------|20| Preparation Phase | Understand before starting | Read plan, verify deps, clarify questions |21| Task Execution | Systematic per-task flow | Read, navigate, implement, verify, complete |22| Progress Tracking | Real-time status updates | Completed X, In Progress Y, Remaining Z |23| Quality Gates | Validation checkpoints | Per-task, per-phase, pre-completion |24| Blocker Resolution | Unblock systematically | Document, assess, attempt, escalate, workaround |25| Deviation Handling | Adapt to discoveries | Document, assess scope/timeline, get approval |2627## Common Patterns2829```30# Task Execution Checklist31BEFORE STARTING:32[ ] Read task description completely33[ ] Understand acceptance criteria34[ ] Check dependencies completed35[ ] No blockers present3637DURING IMPLEMENTATION:38[ ] Navigate to specified files39[ ] Understand existing code context40[ ] Implement changes incrementally41[ ] Write tests alongside code4243AFTER COMPLETION:44[ ] All acceptance criteria met45[ ] Tests pass locally46[ ] No lint/type errors47[ ] Task marked complete4849# Quality Gates50AFTER EACH TASK:51npm run lint && npm run typecheck && npm test -- --related5253AFTER EACH PHASE:54npm run lint && npm run typecheck && npm test && npm run build5556BEFORE COMPLETION:57npm run lint && npm run typecheck && npm test --coverage && npm run build58```5960```61# Progress Report Template62## Status: [Date Time]6364### Summary65- Completed: [N] tasks66- In Progress: [Task name]67- Remaining: [M] tasks68- Blockers: [None | Description]6970### Current Task71**[Task Name]:** [Description]72- Started: [Time]73- Progress: ~60%74- Expected completion: [Time]7576### ETA77On track for [date] | Delayed by [reason]78```7980```81# Blocker Resolution Flow82BLOCKER DETECTED83 |841. DOCUMENT immediately85 - What is blocked?86 - Why is it blocked?87 |882. ASSESS impact89 - Critical path affected?90 - Time sensitive?91 |923. ATTEMPT resolution (15-30 min)93 - Quick research94 - Alternative approach95 |96 +-> RESOLVED -> Continue97 |984. ESCALATE if not resolved99 - Report with: issue, attempts, ask100 |1015. WORK AROUND while waiting102 - Move to non-blocked tasks103```104105## Best Practices106107| Do | Avoid |108|----|-------|109| Read entire plan before starting | Skipping preparation phase |110| Verify understanding of each task | Assuming task requirements |111| Execute tasks in sequence (unless parallel) | Ignoring quality gates |112| Validate after each task completion | Hiding blockers or delays |113| Report blockers immediately | Deviating without documenting |114| Document deviations as they occur | Rushing quality for speed |115| Complete fully before marking done | Leaving tasks partially done |116| Ask questions early | Skipping testing steps |117118## Related Skills119120- `writing-plans` - Create plans to execute121- `verifying-before-completion` - Quality gate checklists122- `thinking-sequentially` - Track execution progress123- `solving-problems` - Resolve blockers systematically124125---126> Converted and distributed by [TomeVault](https://tomevault.io/claim/doanchienthangdev) — claim your Tome and manage your conversions.127<!-- tomevault:4.0:skill_md:2026-04-13 -->
tomevault-io