• Blueprint Development initialized (

  docs/blueprint/

  exists)
• At least one PRD exists (unless using

  --from-issue

  or

  --from-prp

  )

• gh

  CLI authenticated (unless using

  --no-publish

  )

--from-prp NAME

1. Read PRP:
   bash

   cat docs/prps/$NAME.md

2. Extract PRP content:
   • Parse frontmatter for id, confidence score, implements references
   • Extract Objective section
   • Extract Implementation Blueprint tasks
   • Extract TDD Requirements
   • Extract Success Criteria
   • Note ai_docs references
3. Verify confidence:
   • If confidence < 9: Warn that PRP may not be ready for delegation
   • Ask to proceed anyway or return to refine PRP
4. Generate work-order:
   • Pre-populate from PRP content
   • Include relevant ai_docs as inline context (not references)
   • Copy TDD requirements verbatim
   • Include file list from PRP's Codebase Intelligence section
5. Continue to Step 6 (save and optionally publish)

name: blueprint-work-order

--from-issue N

1. Fetch issue:
   bash

   gh issue view N --json title,body,labels,number

2. Parse issue content:
   • Extract objective from title/body
   • Extract any TDD requirements or success criteria if present
   • Note existing labels
3. Generate work-order:
   • Number matches issue number (e.g., issue #42 → work-order

     042-...

     )
   • Pre-populate from issue content
   • Add context sections (files, PRD reference, etc.)
4. Update issue with link:
   bash

   gh issue comment N --body "Work-order created: \`docs/blueprint/work-orders/NNN-task-name.md\`"
   gh issue edit N --add-label "work-order"

5. Continue to save and report (skip to Step 6 below)

• Read

  docs/blueprint/feature-tracker.json

  for current phase and tasks
• Run

  git status

  to check uncommitted work
• Run

  git log -5 --oneline

  to see recent work
• Find existing work-orders (count them for numbering)

• Read PRD files to understand requirements
• Identify next logical work unit based on:
  • Work-overview progress
  • PRD phase/section ordering
  • Git history (what's been done)

• Specific: Single feature/component/fix
• Isolated: Minimal dependencies
• Testable: Clear success criteria
• Focused: 1-4 hours of work

• "Implement JWT token generation methods"
• "Add input validation to registration endpoint"
• "Create database migration for users table"

• "Implement authentication"
• "Fix bugs"

• Files to modify/create (only relevant ones)
• PRD sections (only specific requirements for this task)
• Existing code (only relevant excerpts, not full files)
• Dependencies (external libraries, environment variables)

• Number: Find highest existing work-order number + 1 (001, 002, etc.)
• Name:

  NNN-brief-task-description.md

name: blueprint-work-order
---
id: WO-NNN
created: {YYYY-MM-DD}
status: pending
implements:                    # Source PRP or PRD
  - PRP-NNN
relates-to:                    # Related documents
  - ADR-NNNN
github-issues:
  - N
---

1. Write Test 1 - Run:

   [test_command]

   - Expected: FAIL
2. Implement Test 1 - Run:

   [test_command]

   - Expected: PASS
3. Refactor (if needed) - Run:

   [test_command]

   - Expected: STILL PASS [Repeat for all tests]

• All specified tests written and passing
• [Specific functional requirement met]
• [Performance/security baseline met]
• No regressions (existing tests pass)

• Depends on: Work-Order NNN (if applicable)
• Blocks: Work-Order NNN (if applicable)

name: blueprint-work-order
---

• Implements: {PRP-NNN or PRD-NNN}
• Related ADRs: {list of ADR-NNNN}

• Test 1: [description]
• Test 2: [description]

• [Criterion 1]
• [Criterion 2]

Capture issue number and update work-order file:
```bash

question: "Work-order ready. What would you like to do?"
options:
  - label: "Execute this work-order (Recommended)"
    description: "Start working on the task with TDD workflow"
  - label: "Create another work-order"
    description: "Generate the next task from pending items"
  - label: "Delegate to subagent"
    description: "Hand off for isolated execution"
  - label: "I'm done for now"
    description: "Exit - work-order is saved and ready"

• "Execute this work-order" → Run

  /project:continue

  with work-order context
• "Create another work-order" → Run

  /blueprint:work-order

  again
• "Delegate to subagent" → Provide handoff instructions for subagent execution
• "I'm done" → Exit

name: blueprint-work-order

• Minimal context: Only what's needed, not full files/PRDs
• Specific tests: Exact test cases, not vague descriptions
• TDD enforced: Tests specified before implementation
• Clear criteria: Unambiguous success checkboxes
• Isolated: Task should be doable with only provided context
• Transparent: GitHub issue provides visibility to collaborators

gh

--no-publish

work-order

name: blueprint-work-order

1. Work completed on work-order
2. PR created with

   Fixes #N

   in body/title
3. Work-order moved to

   completed/

   directory
4. Issue auto-closes when PR merges

--no-publish

• Working offline
• Private experimentation
• Issue visibility not needed