execute-plan-using-subagent
Execute Plan Using Subagent
Run an existing plan from the current context without bloating the main context: first spawn an Implementer subagent, then spawn a Reviewer subagent to check the implementation against the plan and project practices.
Quick start
- Extract the current plan from the conversation and restate only the actionable requirements.
- Spawn the Implementer subagent using IMPLEMENTER_PROMPT.md.
- After the Implementer returns, spawn the Reviewer subagent using REVIEWER_PROMPT.md.
- If the Reviewer finds blocking issues, ask the Implementer to fix them or fix them directly if small.
- Report the implementation status, review result, changed files, and verification commands.
Workflow
1. Confirm there is a plan
- Use the plan already present in the current conversation as the source of truth.
- If no concrete plan exists, stop and ask the user for the plan or ask whether to draft one first.
- Do not invent missing requirements. If a decision blocks execution, ask one focused question.
More from ishakantony/skills
discuss
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. DO NOT EVER USE THIS SKILL UNLESS THE USER EXPLICITLY ASKS YOU TO.
19prd-to-issues
Break a PRD into independently-workable issues and write each as a local markdown file in issues/. Use when the user wants to turn a PRD into a list of concrete tasks.
15tdd
Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.
14write-a-prd
Generate a PRD from the client brief and write it as a local markdown file in issues/. Use when the user wants to turn a client request into a structured PRD.
14tackle-issues
Autonomously work through AFK issues from the local issues/ directory in a loop, spawning a subagent per task. Use when user types /tackle-issues or asks to "work the backlog", "burn down issues", "tackle AFK tasks", or run an AFK issue queue. Skips HITL issues. Each task is implemented via TDD in a subagent so the main context stays clean.
13commit
Stage changes, draft conventional commit messages, and commit with user confirmation. Use when user types /commit, asks to commit changes, or mentions creating a git commit.
10