prd-executor

PRD Executor Skill

Overview

This skill guides a Dev Agent through executing a prd_decomposer breakdown located at docs/[Feature_Name]_breakdown/. It enforces three hard gates:

1. Requirements confirmation (brainstorming all 10 closure dimensions) before any coding
2. TDD workflow during implementation
3. Git commit per completed REQ, push per completed Phase

When to Use

• A breakdown directory exists at docs/[Feature_Name]_breakdown/
• User says "start executing", "start development", "implement this PRD", "execute breakdown"
• Dev Agent is handed a breakdown directory and needs to know how to proceed

Workflow

Step 1: Initialize

Read docs/[Feature_Name]_breakdown/outline.md. Extract:

• Total Phases and REQs
• Dependency graph between REQs
• Current status of each REQ (look at the Status column)

Announce to the user: which REQs are pending, which (if any) are already in progress or done.

Step 2: Select Next Phase

Find the first Phase in outline.md whose status is ⬜ (not started) and whose REQ dependencies (if any cross-Phase) are all ✅ or ⚠️.

If no such Phase exists:

• If all Phases are ✅: announce completion, done.
• If a Phase is 💬 or 🔍 or 🚧 or 🧪: resume that Phase from the appropriate stage below.

---

Stage A: Discussion — Discuss All REQs in the Phase [HARD GATE 1]

1. Update Phase status in outline.md to 💬 (Discussing)
2. For each REQ in this Phase, in order: a. Open the REQ file. Check whether 🔍 详细需求确认 still contains ⚠️ [待填充]. b. If YES (placeholder present):
   • Update REQ status in REQ file and outline.md to 💬
   • Invoke superpowers:brainstorming with the REQ content as context
   • Ensure ALL 10 closure dimensions are addressed:
     • API closure
     • Business logic closure
     • UI/UX closure
     • Error handling closure
     • Data consistency closure
     • Permission/security closure
     • Performance boundary closure
     • Testing closure (unit test scenarios + manual UAT checkpoints)
     • Analytics/tracking closure
     • Compatibility closure
   • Replace the entire ⚠️ [待填充] placeholder block with the brainstorming conclusions c. If NO (placeholder already replaced): skip brainstorming for this REQ.
3. YOU ARE FORBIDDEN FROM WRITING ANY IMPLEMENTATION CODE DURING STAGE A