/ultrawork Skill - Automated Development Pipeline

You are initiating an ultrawork session - a fully automated pipeline that chains:

1. •/specify - Interview and plan generation
2. •/open - Draft PR creation
3. •/execute - Implementation

How It Works

The ultrawork pipeline runs automatically through Stop hooks:

• •When you complete Interview (DRAFT.md created) → Hook triggers Plan generation
• •When Plan is approved → Hook triggers /open
• •When PR is created → Hook triggers /execute
• •When all TODOs complete → Pipeline ends

You don't need to manually trigger the next step - the hooks handle transitions.

Your Role

1. •Extract the feature name from user's request
2. •Initialize ultrawork state (CRITICAL - must do before anything else)
3. •Start the specify skill with the feature name
4. •Follow specify's interview process normally
5. •The rest happens automatically via hooks

Execution

Step 1: Parse User Request

Extract a short, kebab-case name for the feature:

• •"Add user authentication" → user-auth
• •"Implement payment processing" → payment-processing
• •"Fix login bug" → fix-login-bug

Note: State initialization is handled automatically by UserPromptSubmit hook (ultrawork-init-hook.sh).

Step 2: Announce Ultrawork Mode

🚀 Ultrawork Mode Activated

Feature: {name}
Pipeline: specify → open → execute

Starting interview phase...

Step 3: Invoke Specify

Skill("specify", args="{name}")

The specify skill will:

1. •Run Interview Mode (gather requirements)
2. •Wait for DRAFT.md to be created
3. •[Hook auto-triggers] → Generate Plan when DRAFT is ready
4. •Run Reviewer approval
5. •[Hook auto-triggers] → Call /open when Plan is approved

Step 4: Let Hooks Handle the Rest

After specify completes with an approved plan:

• •ultrawork-stop-hook.sh detects PLAN.md with "APPROVED"
• •Hook automatically injects /open {name}
• •After PR creation, hook injects /execute
• •Execute runs until all TODOs complete

User Interruption

User can stop the pipeline at any time by saying:

• •"stop"
• •"pause"
• •"wait"

This will halt the current phase and await further instructions.

State Tracking

The hook tracks progress in .dev/state.local.json:

{
  "session-id": {
    "ultrawork": {
      "name": "feature-name",
      "phase": "specify_interview",
      "iteration": 0
    }
  }
}

Phases: specify_interview → specify_plan → opening → executing → done

Example Flow

User: "/ultrawork add dark mode support"

[Hook auto-initializes state for "dark-mode"]

[You]
1. Parse: feature name = "dark-mode"

2. Announce:
   🚀 Ultrawork Mode Activated
   Feature: dark-mode
   Pipeline: specify → open → execute
   Starting interview phase...

3. Invoke: Skill("specify", args="dark-mode")

[Specify Interview runs...]
[DRAFT.md created]
[Hook detects → triggers "Generate the plan"]
[Plan created, Reviewer approves]
[Hook detects → triggers "/open dark-mode"]
[PR created]
[Hook detects → triggers "/execute"]
[TODOs completed]
[Pipeline ends]

Important Notes

• •State is auto-initialized by UserPromptSubmit hook - no manual setup needed
• •Do NOT manually call /open or /execute - hooks handle this
• •Follow specify's interview process - gather requirements properly
• •The pipeline is autonomous - just start it and let it run
• •User can interrupt at any time for manual control