My5t3r10us/cesizen / .agents/skills/apex
apex
VerifiedSystematic implementation using APEX methodology (Analyze-Plan-Execute-eXamine) with optional parallel subagents, self-validation, and adversarial review. Use when implementing features, fixing bugs, or making code changes that benefit from structured workflow.
steps/step-03-execute.md
View on GitHub---
name: step-03-execute
description: Todo-driven implementation - execute the plan file by file
prev_step: steps/step-02-plan.md
next_step: steps/step-04-validate.md
---
# Step 3: Execute (Implementation)
## MANDATORY EXECUTION RULES (READ FIRST):
- π NEVER deviate from the approved plan
- π NEVER add features not in the plan (scope creep)
- π NEVER modify files without reading them first
- β
ALWAYS follow the plan file-by-file
- β
ALWAYS mark todos complete immediately after each task
- β
ALWAYS read files BEFORE editing them
- π YOU ARE AN IMPLEMENTER following a plan, not a designer
- π¬ FOCUS on executing the plan exactly as approved
- π« FORBIDDEN to add "improvements" not in the plan
## EXECUTION PROTOCOLS:
- π― Create todos from plan before starting
- πΎ Mark todos complete immediately after each task
- π Read each file BEFORE modifying it
- π« FORBIDDEN to have multiple todos in_progress simultaneously
## CONTEXT BOUNDARIES:
- Plan from step-02 is approved and must be followed
- Files to modify are known from the plan
- Patterns to follow are documented from step-01
- Don't add features - stick to the plan
- **If context was cleared ("Execute and clear context"):** The plan file contains all APEX state variables in the "APEX Workflow Context" section. Read the plan file first and restore all variables before proceeding.
## YOUR TASK:
Execute the approved implementation plan file-by-file, tracking progress with todos.
---
<available_state>
From previous steps:
| Variable | Description |
|----------|-------------|
| `{task_description}` | What to implement |
| `{task_id}` | Kebab-case identifier |
| `{auto_mode}` | Skip confirmations |
| `{save_mode}` | Save outputs to files |
| `{output_dir}` | Path to output (if save_mode) |
| Implementation plan | File-by-file changes from step-02 |
| Patterns | How to implement from step-01 |
</available_state>
---
## EXECUTION SEQUENCE:
### 1. Initialize Save Output (if save_mode)
**If `{save_mode}` = true:**
```bash
bash {skill_dir}/scripts/update-progress.sh "{task_id}" "03" "execute" "in_progress"
```
Append logs to `{output_dir}/03-execute.md` as you work.
### 2. Create Todos from Plan
Convert each file change from the plan into todos:
```
Plan entry:
#### `src/auth/handler.ts`
- Add `validateToken` function
- Handle error case: expired token
Becomes:
- [ ] src/auth/handler.ts: Add validateToken function
- [ ] src/auth/handler.ts: Handle expired token error
```
Use TodoWrite to create the full list.
### 3. Execute File by File
For each todo:
**3.1 Mark In Progress**
- Only ONE todo in_progress at a time
**3.2 Read Before Edit**
```
ALWAYS read the file before modifying:
- Understand current structure
- Find exact insertion points
- Verify patterns match expectations
```
**3.3 Implement Changes**
```
Make changes specified in the plan:
- Follow patterns from step-01 analysis
- Use exact names from plan
- Handle error cases as specified
- NO comments unless truly necessary
```
**3.4 Mark Complete Immediately**
- Mark todo complete RIGHT AFTER finishing
- Don't batch completions
**3.5 Log Progress (if save_mode)**
```markdown
### β src/auth/handler.ts
- Added `validateToken` function (lines 45-78)
- Added error handling for expired tokens
**Timestamp:** {ISO}
```
### 4. Handle Blockers
**If `{auto_mode}` = true:**
β Make reasonable decision and continue
**If `{auto_mode}` = false:**
```yaml
questions:
- header: "Blocker"
question: "Encountered an issue. How should we proceed?"
options:
- label: "Use alternative approach (Recommended)"
description: "Description of alternative"
- label: "Skip this part"
description: "Continue without this change"
- label: "Stop for discussion"
description: "I want to discuss before continuing"
multiSelect: false
```
### 5. Verify Implementation
After completing all todos:
```bash
bun run type-check && bun run lint
```
Fix any errors immediately.
### 6. Implementation Summary
```
**Implementation Complete**
**Files Modified:**
- `src/auth/handler.ts` - Added validateToken, error handling
- `src/api/auth/route.ts` - Integrated token validation
**New Files:**
- `src/types/auth.ts` - Auth type definitions
**Todos:** {X}/{Y} complete
```
**If `{auto_mode}` = true:**
β Proceed to validation
**If `{auto_mode}` = false:**
```yaml
questions:
- header: "Execute"
question: "Implementation complete. Ready to validate?"
options:
- label: "Proceed to validation (Recommended)"
description: "Run typecheck, lint, and tests"
- label: "Review changes"
description: "I want to review what was changed"
- label: "Make adjustments"
description: "I want to modify something"
multiSelect: false
```
### 7. Complete Save Output (if save_mode)
**If `{save_mode}` = true:**
Append to `{output_dir}/03-execute.md`:
```markdown
---
## Step Complete
**Status:** β Complete
**Files modified:** {count}
**Todos completed:** {count}
**Next:** step-04-validate.md
**Timestamp:** {ISO timestamp}
```
---
## SUCCESS METRICS:
β
All plan items implemented
β
All todos marked complete
β
No scope creep - only plan items
β
Files read before modification
β
Typecheck and lint pass
β
Progress logged (if save_mode)
## FAILURE MODES:
β Adding features not in the plan
β Modifying files without reading first
β Not updating todos as you work
β Multiple todos in_progress simultaneously
β Ignoring type or lint errors
β **CRITICAL**: Not using AskUserQuestion for blockers
## EXECUTION PROTOCOLS:
- Follow the plan EXACTLY
- Read before write
- One file at a time
- Update todos in real-time
- Fix errors immediately
---
## NEXT STEP:
After implementation complete, load `./step-04-validate.md`
<critical>
Remember: Execution is about following the plan - don't redesign or add features!
</critical>
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why β repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" β or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself β your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |