بنقرة واحدة
nobody-executes-plans
Use when you have a written implementation plan to execute with review checkpoints
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Use when you have a written implementation plan to execute with review checkpoints
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when doing any creative work — creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when implementation is complete and all tests pass — guides completion by presenting structured options for merge, PR, or cleanup
Use when receiving code review feedback, before implementing suggestions — requires technical rigor and verification, not performative agreement
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Use when starting feature work that needs isolation from current workspace or before executing implementation plans
| name | nobody-executes-plans |
| description | Use when you have a written implementation plan to execute with review checkpoints |
Execute implementation plans in batches with human checkpoints. Each batch is a logical group of tasks that can be reviewed together.
Announce at start: "I'm using the nobody-executes-plans skill to work through the plan."
For each batch:
### Batch N: [Description]
Tasks: [list from plan]
1. Execute each task following plan exactly
2. Run tests after each task
3. Commit after each task passes
Checkpoint:
- Tasks completed: [list]
- Tests: [pass/fail count]
- Files changed: [list]
- Continue? [y/n]
Update the plan file as you go:
- [x] Task 1: Setup database schema ✅
- [x] Task 2: Add migration script ✅
- [ ] Task 3: Implement CRUD endpoints
- [ ] Task 4: Add validation
| Problem | Action |
|---|---|
| Plan step is unclear | Ask user, don't guess |
| Tests fail unexpectedly | Report full output, wait |
| Plan needs modification | Propose change, get approval |
| Scope creep temptation | Stick to plan, note ideas for later |