بنقرة واحدة
plan-execution
Batch execution with checkpoints. Trigger: When executing plans with batched tasks.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Batch execution with checkpoints. Trigger: When executing plans with batched tasks.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Paste-ready session summary for context transfer to a new chat. Trigger: User says 'context handoff', 'start fresh', or session needs to continue.
One-at-a-time questioning to fully profile a goal before acting. Trigger: User says 'grill me', goal is vague, or clarification is needed first.
Universal coding principles: DRY, security by default, null guards, and YAGNI. Trigger: When writing or reviewing code in any language or technology.
Accessibility guide (WCAG 2.1/2.2, Level A–AAA). Trigger: When building UI components, interactive elements, or auditing accessibility compliance.
Astro quality patterns: island philosophy, SEO by page type, and Core Web Vitals. Trigger: When reviewing Astro site quality or hydration decisions.
Auth patterns: password hashing, JWT, sessions, and OAuth. Trigger: When implementing login, registration, token handling, or OAuth flows.
| name | plan-execution |
| description | Batch execution with checkpoints. Trigger: When executing plans with batched tasks. |
| license | Apache 2.0 |
| metadata | {"version":"1.2","type":"behavioral","skills":["writing-plans","verification-protocol"]} |
Execute plans in batches of 3 tasks with verification checkpoints. Ensures progress tracking and quality gates.
Don't use for:
Execute 3 tasks, then checkpoint before next batch.
### Batch 1: Foundation
#### Task 1: Create User entity (2 min)
**File**: `src/entities/User.ts`
**Implementation**:
[typescript code]
**Status**: Complete
---
**CHECKPOINT**: Batch 1 Complete
**Verification**:
- Ran: `npm test -- UserEntity.test.ts crypto.test.ts UserRepository.test.ts`
- Result: 8/8 tests passed
- Build: `npm run build` → Success
- Lint: `npm run lint` → 0 errors
**Decision**: Proceed to Batch 2
---
### Batch 2: API Layer
[next 3 tasks...]
Why batch size 3?
Verify quality before proceeding.
**CHECKPOINT**: Batch 2 Complete
**Verification**:
1. Tests passing? Yes
- Ran: `npm test`
- Result: 15/15 passed
2. Build succeeds? Yes
- Ran: `npm run build`
- Result: Compiled successfully
3. Lint clean? Yes
- Ran: `npm run lint`
- Result: 0 errors, 0 warnings
4. Type check? Yes
- Ran: `tsc --noEmit`
- Result: No type errors
5. Code quality? Yes
- DRY: no logic duplicated from existing codebase
- Security: no hardcoded secrets, inputs parameterized
- Robustness: null guards present, no swallowed exceptions
- YAGNI: no unused abstractions or dead config
**Architect Review Needed?** No (straightforward CRUD implementation)
**Blockers?** None
**Decision**: Proceed to Batch 3
Checkpoint serves as:
Track overall progress across batches.
### Overall Progress
**Completed Batches**: 2/4 (50%)
**Completed Tasks**: 6/12 (50%)
**Current Batch**: Batch 3 (tasks 7-9)
**Remaining**: Batch 4 (tasks 10-12)
**Status**: On track
**Blockers**: None
**Risks**: None identified
**Timeline**:
- Batch 1: Completed 2:15 PM (7 min)
- Batch 2: Completed 2:28 PM (9 min)
- Batch 3: In progress (started 2:30 PM)
- Batch 4: Not started
**Estimated completion**: 3:00 PM (30 min total)
Benefits:
Escalate for review when needed.
**CHECKPOINT**: Batch 2 Complete
**Architect Review Required**: YES
**Reason**:
- API versioning strategy decision needed
- Breaking change to /users endpoint (removing deprecated fields)
**Questions for Architect**:
1. Preferred approach: /v2/users or query param ?version=2?
2. Deprecation timeline: immediate or gradual?
**Blocking**: Cannot proceed to Batch 3 until architect approves approach
[After architect feedback]
**Architect Decision**: Use /v2/users, 3-month deprecation for /v1/users
**Decision**: Resume execution
When to escalate:
Executing a plan?
→ Group into batches of 3 tasks
→ Execute batch sequentially
→ Checkpoint (verify all 3 tasks)
→ Architect review needed?
→ YES: Escalate, document questions, wait for decision
→ NO: Proceed to next batch
→ Repeat until all batches complete
Task blocked?
→ Document blocker clearly
→ Skip to next unblocked task (if possible)
→ Return to blocked task after resolution
Quality issue at checkpoint?
→ STOP execution
→ Identify root cause
→ Fix issues in current batch
→ Re-verify checkpoint
→ Only then proceed
Code quality issue at checkpoint?
Security violation (hardcoded secret, input not parameterized)?
→ STOP immediately — fix before proceeding
DRY, robustness, or YAGNI issue?
→ Fix in current batch before marking checkpoint passed
Task taking longer than planned?
→ Note actual time
→ Adjust estimates for remaining tasks
→ Flag if timeline at risk
Three-batch execution of an auth module implementation:
### Batch 1: Data layer (tasks 1-3)
Task 1: User entity — src/entities/User.ts ✅
Task 2: UserRepository — src/repositories/UserRepository.ts ✅
Task 3: Password hashing util — src/utils/hash.ts ✅
**CHECKPOINT**: Batch 1 Complete
- npm test → 8/8 passed
- npm run build → Success
- Decision: Proceed to Batch 2
### Batch 2: API layer (tasks 4-6)
Task 4: POST /auth/login ✅
Task 5: POST /auth/refresh ✅
Task 6: POST /auth/logout ✅
**CHECKPOINT**: Batch 2 Complete
- npm test → 15/15 passed
- Architect review needed? No (standard JWT pattern)
- Decision: Proceed to Batch 3
Task dependencies within batch: If Task 2 depends on Task 1, that's fine. If Task 5 depends on Task 2 (cross-batch), ensure checkpoint captures that dependency.
Partial batch completion: If only 2 of 3 tasks done (blocker on Task 3), checkpoint what's done, escalate blocker.
**CHECKPOINT**: Batch 2 PARTIAL (2/3 complete)
**Completed**:
- Task 4
- Task 5
**Blocked**:
- Task 6: External API credentials missing
- **Blocker**: Need API key from DevOps team
- **ETA**: 2 hours
**Decision**: Proceed to Batch 3 (tasks 7-9), return to Task 6 later
Critical failure: If checkpoint fails badly (many tests broken, build fails), stop and roll back.
**CHECKPOINT**: Batch 3 FAILED
**Issue**: 12 tests failing after refactor
**Root cause**: Breaking change in User interface
**Impact**: High - core functionality broken
**Decision**: STOP and ROLLBACK
- Revert commits from Batch 3
- Return to Batch 2 (last known good state)
- Re-plan Batch 3 with different approach
Fast batches (<5 min total): Combine next batch if work is trivial. Example: "Batch 2+3 combined (6 small tasks, 8 min total)".