subagent-driven-developmentlisted

# Subagent-Driven Development Execute an existing `3-PLAN.md` by dispatching a fresh subagent for each task, then running two review loops after each task: spec compliance first, code quality second. **Announce at start:** "I'm using the subagent-driven-development skill to implement this plan." **Core principle:** fresh subagent per task + spec review + quality review = focused implementation with verification before progress. ## When to Use Use this skill when: - A `3-PLAN.md` implementation plan already exists. - Tasks are mostly independent or clearly sequenced. - You want to stay in this Pi session as coordinator. - Subagent tools are available. Use the Pi-adapted `executing-plans` skill instead when: - Subagent tools are unavailable. - Tasks are tightly coupled and need one continuous implementation context. - The user wants batch execution with manual checkpoints instead of per-task delegation. ## The Process ### Step 1: Locate and Review the Plan 1. Use the plan path provided by the user, or ask for it if none was provided. 2. If no path is provided and an active `~/.pi/plans/...` task folder is known, read `3-PLAN.md` from that folder. 3. If `3-PLAN.md` is missing, stop and ask for the correct plan path. 4. Review the plan for contradictions, missing verification commands, unclear tasks, or unsafe commit instructions. 5. Raise blocking concerns with the user before editing files or dispatching subagents. 6. Confirm you are not on `main` or `master` before