| name | redsub-execute |
| description | Execute implementation plan task-by-task with subagent dispatch and 2-stage review. |
Plan Execution
Announce: "Using /redsub-execute to implement the plan."
Invoke superpowers:executing-plans skill first, then apply these additional conventions:
Input
$ARGUMENTS: path to plan document (e.g., docs/plans/2025-01-15-auth-plan.md).
redsub Conventions
Subagent Dispatch Model
Instead of superpowers' batch execution model, use subagent dispatch per task:
a. Dispatch Implementer (Task tool)
Prompt structure for implementer subagent:
Context: [Project description, current state]
Task: [Full task text from plan, verbatim]
Constraints:
- Follow TDD: write failing test first, verify failure, then implement
- Do NOT modify files outside this task's scope
- Commit when done: `type: description` (redsub commit convention)
- e.g., `feat: add user authentication API`, `fix: handle null pointer exception`
Expected output:
- What was implemented
- Test results (actual output)
- Files created/modified
- Commit SHA
b. 2-Stage Review
After each implementer completes:
Stage 1: Spec Compliance Review (Task tool)
- Does implementation match plan spec exactly?
- Are all required files created/modified?
- Do tests cover the spec requirements?
- Any over-building or under-building?
- Output: PASS or FAIL with specific issues.
- FAIL → implementer fixes → re-review.
Stage 2: Code Quality Review (Task tool)
- Code clarity and readability
- Error handling and edge cases
- No security vulnerabilities
- Follows project conventions (CLAUDE.md)
- Output: APPROVED or issues list with severity.
