Create a work-order for isolated subagent execution, optionally linked to a GitHub issue. Use when breaking a PRP into delegatable tasks or spawning from an issue.
Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.
Quelldateien prüfen
Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.
Create a work-order for isolated subagent execution, optionally linked to a GitHub issue. Use when breaking a PRP into delegatable tasks or spawning from an issue.
args
[--no-publish] [--from-issue N]
argument-hint
--no-publish for local-only, --from-issue 123 to create from existing issue
disable-model-invocation
true
allowed-tools
Read, Write, Glob, Bash, AskUserQuestion
name
blueprint-work-order
Generate a work-order document for isolated subagent execution with optional GitHub issue integration.
When to Use This Skill
Use this skill when...
Use blueprint-prp-create instead when...
You're breaking a PRP into delegatable subagent tasks
You're creating the PRP itself with full research and validation gates
You want a focused TDD task packet with minimal context
You need a comprehensive context-gathered implementation plan
You want to spawn a work-order from an existing PRP (--from-prp)
Use blueprint-prp-execute instead when running an already-written PRP
You're creating a work-order from a GitHub issue (--from-issue)
Use confidence-scoring instead to evaluate readiness before delegating
Flags
Flag
Description
--no-publish
Create local work-order only, skip GitHub issue creation
--from-issue N
Create work-order from existing GitHub issue #N (a work-order-draft proposal issue is promoted: packet consumed, label swapped to work-order)
--from-prp NAME
Create work-order from existing PRP (auto-populates context)
Default behavior: Creates both local work-order AND GitHub issue with work-order label.
Interaction Mode
Before any closing AskUserQuestion menu, resolve the automation config:
When EFFECTIVE_INTERACTION_MODE=quietand this invocation was
automation-initiated (autopilot, session bookend, drift-nudge follow-up — not
a slash command the user typed), skip closing navigation menus ("what next?" /
"create another?" style): apply the safe default and end with a one-line
receipt instead. Quiet mode never skips confirmation gates that guard writes —
only navigation menus. A direct user invocation always behaves fully
interactively (explicit intent overrides quiet; see ADR-0020).
Prerequisites
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)
Mode: Create from PRP (--from-prp NAME)
When --from-prp NAME is provided:
Read PRP:
cat docs/prps/$NAME.md
Extract PRP content:
Parse frontmatter for id, confidence score, implements references
If confidence < 9: Warn that PRP may not be ready for delegation
Ask to proceed anyway or return to refine PRP
Generate work-order:
Pre-populate from PRP content
Include relevant curated rules as inline context (not references)
Copy TDD requirements verbatim
Include file list from PRP's Codebase Intelligence section
Continue to Step 6 (save and optionally publish)
Mode: Create from Existing Issue (--from-issue N)
When --from-issue N is provided:
Fetch issue:
gh issue view N --json title,body,labels,number
Parse issue content:
Extract objective from title/body
Extract any TDD requirements or success criteria if present
Note existing labels
2a. Promote a work-order-draft proposal (ADR-0020 auto-draft channel):
If the issue carries the work-order-draft label, it is an auto-drafted
proposal from /blueprint:autopilot — its body already IS the full
work-order packet (title form [work-order-draft] PRP-NNN: <title>).
Promotion is the human committing act the draft channel preserves:
Consume the packet verbatim as the work-order content (the draft body
supersedes step 3's re-generation; still verify the referenced PRP exists
and its confidence is current — warn if it dropped below 9)
In step 4, additionally swap the labels:
gh issue edit N --remove-label "work-order-draft" --add-label "work-order"
Proceed with the normal save path (Step 6): the local WO file,
feature-tracker.jsontasks.pending, and the manifest id_registry
mutate HERE, at promotion — never at draft time
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.)
Update issue with link:
gh issue comment N --body "Work-order created: \`docs/blueprint/work-orders/NNN-task-name.md\`"# Ensure the label exists before applying itif ! gh label list --search "work-order" --json name | jq -e '.[] | select(.name=="work-order")' >/dev/null 2>&1; then
gh label create work-order --description "AI-assisted work order" --color "0E8A16"fi
gh issue edit N --add-label "work-order"
Continue to save and report (skip to Step 6 below)
Mode: Create New Work-Order (Default)
Step 1: Analyze Current State
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)
Step 2: Read Relevant PRDs
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)
Step 3: Determine Next Work Unit
Should be:
Specific: Single feature/component/fix
Isolated: Minimal dependencies
Testable: Clear success criteria
Focused: 1-4 hours of work
Good examples:
"Implement JWT token generation methods"
"Add input validation to registration endpoint"
"Create database migration for users table"
Bad examples (too broad):
"Implement authentication"
"Fix bugs"
Step 4: Determine Minimal Context
Files to modify/create (only relevant ones)
PRD sections (only specific requirements for this task)
Existing code (only relevant excerpts, not full files)
Also update the source PRP/PRD to add this work-order to its tracking.
Step 9: Report
Work-order created!
ID: WO-NNN
Work-Order: 003-jwt-token-generation.md
Location: docs/blueprint/work-orders/003-jwt-token-generation.md
GitHub Issue: #42 (or "Local only" if --no-publish)
Traceability:
- Implements: PRP-002 (OAuth Integration)
- Related: ADR-0003 (Session Storage)
Objective: [Brief objective]
Context included:
- Files: [List files]
- Tests: [Number of tests specified]
- Dependencies: [Key dependencies]
Ready for execution:
- Can be executed by subagent with isolated context
- TDD workflow enforced (tests specified first)
- Clear success criteria defined
- PR should use "Fixes #42" to auto-close issue
- Commit messages should use: feat(WO-NNN): description
Step 10: Prompt for Next Action
Use AskUserQuestion:
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"
Based on selection:
"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
Key Principles
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
Error Handling
Condition
Action
No PRDs exist
Guide to write PRDs first
No tasks in feature-tracker
Ask for current phase/status
Task unclear
Ask user what to work on next
gh not authenticated
Warn and fallback to --no-publish behavior
Issue already has work-order label
Warn, ask to update or create new
GitHub Integration Notes
Completion Flow
Work completed on work-order
PR created with Fixes #N in body/title
Work-order moved to completed/ directory
Issue auto-closes when PR merges
Label Convention
The work-order label identifies issues created from this workflow. Create it in your repo if it doesn't exist:
gh label create work-order --description "AI-assisted work order" --color "0E8A16"
Offline Mode
Use --no-publish when:
Working offline
Private experimentation
Issue visibility not needed
Can publish later by manually creating issue and updating work-order file.
