maestro-flow 0.3.9 → 0.3.11

package/workflows/quick.md

@@ -1,497 +1,497 @@
-# Quick Task Workflow
-
-Execute small, ad-hoc tasks with workflow guarantees (atomic commits, state tracking). Quick mode spawns workflow-planner (quick mode) + workflow-executor(s), tracks tasks in `.workflow/scratch/`, and updates state.json.
-
-With `--discuss`: lightweight decision extraction before planning. Identifies gray areas, conducts interactive discussion, classifies decisions as Locked/Free/Deferred in context.md so the planner treats Locked decisions as constraints and Free decisions as implementer discretion.
-
-With `--full`: enables plan-checking (max 2 iterations) and post-execution verification.
-
-Flags are composable: `--discuss --full` gives discussion + plan-checking + verification.
-
----
-
-## Prerequisites
-
-- `.workflow/state.json` must exist (project initialized)
-- Quick tasks can run mid-phase -- validation only checks project exists, not phase status
-
----
-
-### Step 1: Parse Arguments
-
-**Parse $ARGUMENTS for flags and description:**
-
-Extract:
-- `--full` flag -> store as `$FULL_MODE` (true/false)
-- `--discuss` flag -> store as `$DISCUSS_MODE` (true/false)
-- Remaining text -> use as `$DESCRIPTION`
-
-If `$DESCRIPTION` is empty after parsing:
-```
-AskUserQuestion(
-  header: "Quick Task",
-  question: "What do you want to do?",
-  followUp: null
-)
-```
-
-Store response as `$DESCRIPTION`.
-If still empty, re-prompt: "Please provide a task description."
-
-Display banner based on active flags:
-
-If `$DISCUSS_MODE` and `$FULL_MODE`:
-```
-------------------------------------------------------------
-  WORKFLOW > QUICK TASK (DISCUSS + FULL)
-------------------------------------------------------------
-Discussion + plan checking + verification enabled
-```
-
-If `$DISCUSS_MODE` only:
-```
-------------------------------------------------------------
-  WORKFLOW > QUICK TASK (DISCUSS)
-------------------------------------------------------------
-Discussion phase enabled -- surfacing gray areas before planning
-```
-
-If `$FULL_MODE` only:
-```
-------------------------------------------------------------
-  WORKFLOW > QUICK TASK (FULL MODE)
-------------------------------------------------------------
-Plan checking + verification enabled
-```
-
-Default (no flags):
-```
-------------------------------------------------------------
-  WORKFLOW > QUICK TASK
-------------------------------------------------------------
-```
-
----
-
-### Step 2: Validate Project
-
-**Validate project state:**
-
-Check .workflow/ exists and has state.json:
-```bash
-test -f .workflow/state.json && echo "exists" || echo "missing"
-```
-
-If missing: Error -- "Quick mode requires an initialized project. Run /workflow:init first."
-
-Quick tasks can run mid-phase -- validation only checks project exists, not phase status.
-
----
-
-### Step 3: Create Scratch Directory
-
-**Create scratch directory:**
-
-Generate slug from $DESCRIPTION (lowercase, hyphens, max 40 chars).
-Set date to current date (YYYY-MM-DD).
-
-```bash
-QUICK_DIR=".workflow/scratch/quick-${slug}-${date}"
-mkdir -p "$QUICK_DIR/.task"
-mkdir -p "$QUICK_DIR/.summaries"
-```
-
-Write index.json:
-```json
-{
-  "id": "quick-{slug}-{date}",
-  "type": "quick",
-  "title": "{$DESCRIPTION}",
-  "status": "active",
-  "created_at": "{ISO timestamp}",
-  "updated_at": "{ISO timestamp}",
-  "flags": {
-    "discuss": {$DISCUSS_MODE},
-    "full": {$FULL_MODE}
-  },
-  "plan": {
-    "task_ids": [],
-    "task_count": 0
-  },
-  "execution": {
-    "method": "agent",
-    "tasks_completed": 0,
-    "tasks_total": 0
-  }
-}
-```
-
-Report: "Creating quick task: {$DESCRIPTION}\nDirectory: {$QUICK_DIR}"
-
----
-
-### Step 4: Discussion Phase (only when $DISCUSS_MODE)
-
-**Lightweight discussion:**
-
-Skip entirely if NOT $DISCUSS_MODE.
-
-```
-------------------------------------------------------------
-  WORKFLOW > DISCUSSING QUICK TASK
-------------------------------------------------------------
-Surfacing gray areas for: {$DESCRIPTION}
-```
-
-**4a. Identify gray areas:**
-
-Analyze $DESCRIPTION to identify 2-4 gray areas -- implementation decisions that would change the outcome. Use domain-aware heuristic:
-- Something users **SEE** -> layout, density, interactions, states
-- Something users **CALL** -> responses, errors, auth, versioning
-- Something users **RUN** -> output format, flags, modes, error handling
-- Something users **READ** -> structure, tone, depth, flow
-- Something being **ORGANIZED** -> criteria, grouping, naming, exceptions
-
-**4b. Present gray areas:**
-
-```
-AskUserQuestion(
-  header: "Gray Areas",
-  question: "Which areas need clarification before planning?",
-  options: [
-    { label: "{area_1}", description: "{why_it_matters}" },
-    { label: "{area_2}", description: "{why_it_matters}" },
-    { label: "{area_3}", description: "{why_it_matters}" },
-    { label: "All clear", description: "Skip discussion -- I know what I want" }
-  ],
-  multiSelect: true
-)
-```
-
-If user selects "All clear" -> skip to Step 5 (no context.md written).
-
-**4c. Discuss selected areas:**
-
-For each selected area, ask 1-2 focused questions:
-```
-AskUserQuestion(
-  header: "{area_name}",
-  question: "{specific question}",
-  options: [
-    { label: "{choice_1}", description: "{what this means}" },
-    { label: "{choice_2}", description: "{what this means}" },
-    { label: "You decide", description: "Claude's discretion" }
-  ]
-)
-```
-
-Max 2 questions per area. Collect all decisions.
-
-**4d. Classify decisions:**
-
-- **Locked**: firm decisions that cannot be changed during implementation
-- **Free**: open for implementation discretion (implementer can choose)
-- **Deferred**: postponed (captured but not acted on in this quick task)
-
-**4e. Write context.md:**
-
-```markdown
-# Quick Task: {$DESCRIPTION} - Context
-
-**Gathered:** {date}
-**Status:** Ready for planning
-
-## Task Boundary
-
-{$DESCRIPTION}
-
-## Constraints
-
-### Locked
-{decisions that are final and must be followed}
-
-### Free
-{decisions left to implementer discretion, including "You decide" areas}
-
-### Deferred
-{ideas captured but out of scope for this quick task}
-
-## Code Context
-{relevant code references from discussion, if any}
-```
-
-Write to `${QUICK_DIR}/context.md`.
-Report: "Context captured: ${QUICK_DIR}/context.md"
-
----
-
-### Step 4.5: Load Project Specs
-
-```
-specs_content = maestro spec load --category execution
-```
-
-Passed inline to planner agent in Step 5.
-
----
-
-### Step 5: Spawn Planner
-
-**Spawn workflow-planner in quick mode:**
-
-```
-Task(
-  prompt="
-<planning_context>
-
-**Mode:** ${FULL_MODE ? 'quick-full' : 'quick'}
-**Directory:** ${QUICK_DIR}
-**Description:** ${DESCRIPTION}
-
-Read these files:
-- .workflow/state.json (Project state)
-- ./CLAUDE.md (Project instructions, if exists)
-
-Project specs (pre-loaded in Step 4.5):
-${specs_content || 'No specs found.'}
-${DISCUSS_MODE ? '- ' + QUICK_DIR + '/context.md (User decisions -- locked)' : ''}
-
-</planning_context>
-
-<constraints>
-- Create a SINGLE plan with 1-3 focused tasks
-- Quick tasks should be atomic and self-contained
-- No research phase
-${FULL_MODE ? '- Target ~40% context usage (structured for verification)' : '- Target ~30% context usage (simple, focused)'}
-${FULL_MODE ? '- Each task MUST have files, action, convergence.criteria, implementation fields' : ''}
-</constraints>
-
-<output>
-Write plan to: ${QUICK_DIR}/plan.json
-Write tasks to: ${QUICK_DIR}/.task/TASK-{NNN}.json
-Return: ## PLANNING COMPLETE with plan path
-</output>
-",
-  subagent_type="workflow-planner",
-  description="Quick plan: ${DESCRIPTION}"
-)
-```
-
-After planner returns:
-1. Verify plan.json exists at `${QUICK_DIR}/plan.json`
-2. Update index.json plan fields
-3. Report: "Plan created: ${QUICK_DIR}/plan.json"
-
-If plan not found: "Planner failed to create plan.json"
-
----
-
-### Step 6: Plan Checker (only when $FULL_MODE)
-
-**Plan-checker loop:**
-
-Skip entirely if NOT $FULL_MODE.
-
-```
-------------------------------------------------------------
-  WORKFLOW > CHECKING PLAN
-------------------------------------------------------------
-Spawning plan checker...
-```
-
-```
-Task(
-  prompt="
-Verify quick task plan.
-
-Read: ${QUICK_DIR}/plan.json and ${QUICK_DIR}/.task/TASK-*.json
-
-Check dimensions:
-- Requirement coverage: Does the plan address the task description?
-- Task completeness: Do tasks have files, action, convergence.criteria, implementation?
-- Scope sanity: Appropriately sized for quick task (1-3 tasks)?
-${DISCUSS_MODE ? '- Context compliance: Does plan honor decisions from context.md?' : ''}
-
-Return one of:
-- ## VERIFICATION PASSED
-- ## ISSUES FOUND -- structured issue list
-",
-  subagent_type="workflow-plan-checker",
-  description="Check quick plan: ${DESCRIPTION}"
-)
-```
-
-**Handle checker return:**
-
-- **VERIFICATION PASSED:** Continue to Step 7.
-- **ISSUES FOUND:** Enter revision loop.
-
-**Revision loop (max 2 iterations):**
-
-If iteration_count < 2:
-- Display: "Sending back to planner for revision... (iteration {N}/2)"
-- Spawn planner with revision context + checker issues
-- Re-check with checker
-- Increment iteration_count
-
-If iteration_count >= 2:
-- Display: "Max iterations reached. {N} issues remain."
-- Offer: 1) Force proceed, 2) Abort
-
----
-
-### Step 7: Spawn Executor
-
-**Spawn workflow-executor:**
-
-```
-Task(
-  prompt="
-Execute quick task.
-
-Read:
-- ${QUICK_DIR}/plan.json (Plan)
-- ${QUICK_DIR}/.task/TASK-*.json (Tasks)
-- .workflow/state.json (Project state)
-- ./CLAUDE.md (Project instructions, if exists)
-
-Constraints:
-- Execute all tasks in the plan
-- Commit each task atomically
-- Create summary for each task at: ${QUICK_DIR}/.summaries/TASK-{NNN}-summary.md
-",
-  subagent_type="workflow-executor",
-  description="Execute: ${DESCRIPTION}"
-)
-```
-
-After executor returns:
-1. Verify summaries exist
-2. Update index.json execution fields
-3. Report completion status
-
----
-
-### Step 8: Verification (only when $FULL_MODE)
-
-**Post-execution verification:**
-
-Skip entirely if NOT $FULL_MODE.
-
-```
-------------------------------------------------------------
-  WORKFLOW > VERIFYING RESULTS
-------------------------------------------------------------
-Spawning verifier...
-```
-
-```
-Task(
-  prompt="
-Verify quick task goal achievement.
-Task directory: ${QUICK_DIR}
-Task goal: ${DESCRIPTION}
-
-Read: ${QUICK_DIR}/plan.json and ${QUICK_DIR}/.summaries/
-
-Check plan objectives against actual codebase.
-Write verification result to: ${QUICK_DIR}/verification.json
-",
-  subagent_type="workflow-verifier",
-  description="Verify: ${DESCRIPTION}"
-)
-```
-
-Read verification result:
-| Status | Action |
-|--------|--------|
-| passed | Store "Verified", continue |
-| gaps_found | Display gaps, offer: 1) Re-run executor, 2) Accept as-is |
-
----
-
-### Step 9: Update State
-
-**Update state.json:**
-
-Read state.json. Add quick task to accumulated_context or quick_tasks array.
-
-Record:
-```json
-{
-  "id": "quick-{slug}-{date}",
-  "description": "{$DESCRIPTION}",
-  "completed_at": "{ISO timestamp}",
-  "directory": "{$QUICK_DIR}",
-  "verified": {$FULL_MODE ? verification_status : "skipped"}
-}
-```
-
-Update last_updated timestamp.
-
----
-
-### Step 10: Commit and Complete
-
-**Final commit and completion:**
-
-Update index.json status to "completed".
-
-Commit quick task artifacts:
-```bash
-git add "${QUICK_DIR}/" .workflow/state.json
-git commit -m "quick({slug}): ${DESCRIPTION}"
-```
-
-Display completion:
-
-If $FULL_MODE:
-```
-------------------------------------------------------------
-  WORKFLOW > QUICK TASK COMPLETE (FULL MODE)
-------------------------------------------------------------
-
-Quick Task: {$DESCRIPTION}
-
-Summary: ${QUICK_DIR}/.summaries/
-Verification: ${QUICK_DIR}/verification.json ({status})
-Directory: ${QUICK_DIR}
-
-------------------------------------------------------------
-Ready for next task: /workflow:quick
-```
-
-If NOT $FULL_MODE:
-```
-------------------------------------------------------------
-  WORKFLOW > QUICK TASK COMPLETE
-------------------------------------------------------------
-
-Quick Task: {$DESCRIPTION}
-
-Summary: ${QUICK_DIR}/.summaries/
-Directory: ${QUICK_DIR}
-
-------------------------------------------------------------
-Ready for next task: /workflow:quick
-```
-
----
-
-## Success Criteria
-
-- [ ] --full and --discuss flags parsed from arguments when present
-- [ ] Flags are composable (--discuss --full works)
-- [ ] User provides task description (prompted if missing)
-- [ ] Project validated (state.json exists)
-- [ ] Scratch directory created at .workflow/scratch/quick-{slug}-{date}/
-- [ ] index.json created in scratch dir
-- [ ] (--discuss) Gray areas identified, decisions captured in context.md
-- [ ] (--discuss) context.md honors "All clear" skip and "You decide" discretion
-- [ ] plan.json + .task/TASK-*.json created by planner
-- [ ] (--full) Plan checker validates plan, revision loop capped at 2
-- [ ] .summaries/TASK-*-summary.md created by executor
-- [ ] (--full) verification.json created by verifier
-- [ ] state.json updated with quick task record
-- [ ] Artifacts committed
-- [ ] index.json status set to "completed"
+# Quick Task Workflow
+
+Execute small, ad-hoc tasks with workflow guarantees (atomic commits, state tracking). Quick mode spawns workflow-planner (quick mode) + workflow-executor(s), tracks tasks in `.workflow/scratch/`, and updates state.json.
+
+With `--discuss`: lightweight decision extraction before planning. Identifies gray areas, conducts interactive discussion, classifies decisions as Locked/Free/Deferred in context.md so the planner treats Locked decisions as constraints and Free decisions as implementer discretion.
+
+With `--full`: enables plan-checking (max 2 iterations) and post-execution verification.
+
+Flags are composable: `--discuss --full` gives discussion + plan-checking + verification.
+
+---
+
+## Prerequisites
+
+- `.workflow/state.json` must exist (project initialized)
+- Quick tasks can run mid-phase -- validation only checks project exists, not phase status
+
+---
+
+### Step 1: Parse Arguments
+
+**Parse $ARGUMENTS for flags and description:**
+
+Extract:
+- `--full` flag -> store as `$FULL_MODE` (true/false)
+- `--discuss` flag -> store as `$DISCUSS_MODE` (true/false)
+- Remaining text -> use as `$DESCRIPTION`
+
+If `$DESCRIPTION` is empty after parsing:
+```
+AskUserQuestion(
+  header: "Quick Task",
+  question: "What do you want to do?",
+  followUp: null
+)
+```
+
+Store response as `$DESCRIPTION`.
+If still empty, re-prompt: "Please provide a task description."
+
+Display banner based on active flags:
+
+If `$DISCUSS_MODE` and `$FULL_MODE`:
+```
+------------------------------------------------------------
+  WORKFLOW > QUICK TASK (DISCUSS + FULL)
+------------------------------------------------------------
+Discussion + plan checking + verification enabled
+```
+
+If `$DISCUSS_MODE` only:
+```
+------------------------------------------------------------
+  WORKFLOW > QUICK TASK (DISCUSS)
+------------------------------------------------------------
+Discussion phase enabled -- surfacing gray areas before planning
+```
+
+If `$FULL_MODE` only:
+```
+------------------------------------------------------------
+  WORKFLOW > QUICK TASK (FULL MODE)
+------------------------------------------------------------
+Plan checking + verification enabled
+```
+
+Default (no flags):
+```
+------------------------------------------------------------
+  WORKFLOW > QUICK TASK
+------------------------------------------------------------
+```
+
+---
+
+### Step 2: Validate Project
+
+**Validate project state:**
+
+Check .workflow/ exists and has state.json:
+```bash
+test -f .workflow/state.json && echo "exists" || echo "missing"
+```
+
+If missing: Error -- "Quick mode requires an initialized project. Run /workflow:init first."
+
+Quick tasks can run mid-phase -- validation only checks project exists, not phase status.
+
+---
+
+### Step 3: Create Scratch Directory
+
+**Create scratch directory:**
+
+Generate slug from $DESCRIPTION (lowercase, hyphens, max 40 chars).
+Set date to current date (YYYY-MM-DD).
+
+```bash
+QUICK_DIR=".workflow/scratch/quick-${slug}-${date}"
+mkdir -p "$QUICK_DIR/.task"
+mkdir -p "$QUICK_DIR/.summaries"
+```
+
+Write index.json:
+```json
+{
+  "id": "quick-{slug}-{date}",
+  "type": "quick",
+  "title": "{$DESCRIPTION}",
+  "status": "active",
+  "created_at": "{ISO timestamp}",
+  "updated_at": "{ISO timestamp}",
+  "flags": {
+    "discuss": {$DISCUSS_MODE},
+    "full": {$FULL_MODE}
+  },
+  "plan": {
+    "task_ids": [],
+    "task_count": 0
+  },
+  "execution": {
+    "method": "agent",
+    "tasks_completed": 0,
+    "tasks_total": 0
+  }
+}
+```
+
+Report: "Creating quick task: {$DESCRIPTION}\nDirectory: {$QUICK_DIR}"
+
+---
+
+### Step 4: Discussion Phase (only when $DISCUSS_MODE)
+
+**Lightweight discussion:**
+
+Skip entirely if NOT $DISCUSS_MODE.
+
+```
+------------------------------------------------------------
+  WORKFLOW > DISCUSSING QUICK TASK
+------------------------------------------------------------
+Surfacing gray areas for: {$DESCRIPTION}
+```
+
+**4a. Identify gray areas:**
+
+Analyze $DESCRIPTION to identify 2-4 gray areas -- implementation decisions that would change the outcome. Use domain-aware heuristic:
+- Something users **SEE** -> layout, density, interactions, states
+- Something users **CALL** -> responses, errors, auth, versioning
+- Something users **RUN** -> output format, flags, modes, error handling
+- Something users **READ** -> structure, tone, depth, flow
+- Something being **ORGANIZED** -> criteria, grouping, naming, exceptions
+
+**4b. Present gray areas:**
+
+```
+AskUserQuestion(
+  header: "Gray Areas",
+  question: "Which areas need clarification before planning?",
+  options: [
+    { label: "{area_1}", description: "{why_it_matters}" },
+    { label: "{area_2}", description: "{why_it_matters}" },
+    { label: "{area_3}", description: "{why_it_matters}" },
+    { label: "All clear", description: "Skip discussion -- I know what I want" }
+  ],
+  multiSelect: true
+)
+```
+
+If user selects "All clear" -> skip to Step 5 (no context.md written).
+
+**4c. Discuss selected areas:**
+
+For each selected area, ask 1-2 focused questions:
+```
+AskUserQuestion(
+  header: "{area_name}",
+  question: "{specific question}",
+  options: [
+    { label: "{choice_1}", description: "{what this means}" },
+    { label: "{choice_2}", description: "{what this means}" },
+    { label: "You decide", description: "Claude's discretion" }
+  ]
+)
+```
+
+Max 2 questions per area. Collect all decisions.
+
+**4d. Classify decisions:**
+
+- **Locked**: firm decisions that cannot be changed during implementation
+- **Free**: open for implementation discretion (implementer can choose)
+- **Deferred**: postponed (captured but not acted on in this quick task)
+
+**4e. Write context.md:**
+
+```markdown
+# Quick Task: {$DESCRIPTION} - Context
+
+**Gathered:** {date}
+**Status:** Ready for planning
+
+## Task Boundary
+
+{$DESCRIPTION}
+
+## Constraints
+
+### Locked
+{decisions that are final and must be followed}
+
+### Free
+{decisions left to implementer discretion, including "You decide" areas}
+
+### Deferred
+{ideas captured but out of scope for this quick task}
+
+## Code Context
+{relevant code references from discussion, if any}
+```
+
+Write to `${QUICK_DIR}/context.md`.
+Report: "Context captured: ${QUICK_DIR}/context.md"
+
+---
+
+### Step 4.5: Load Project Specs
+
+```
+specs_content = maestro spec load --category coding
+```
+
+Passed inline to planner agent in Step 5.
+
+---
+
+### Step 5: Spawn Planner
+
+**Spawn workflow-planner in quick mode:**
+
+```
+Task(
+  prompt="
+<planning_context>
+
+**Mode:** ${FULL_MODE ? 'quick-full' : 'quick'}
+**Directory:** ${QUICK_DIR}
+**Description:** ${DESCRIPTION}
+
+Read these files:
+- .workflow/state.json (Project state)
+- ./CLAUDE.md (Project instructions, if exists)
+
+Project specs (pre-loaded in Step 4.5):
+${specs_content || 'No specs found.'}
+${DISCUSS_MODE ? '- ' + QUICK_DIR + '/context.md (User decisions -- locked)' : ''}
+
+</planning_context>
+
+<constraints>
+- Create a SINGLE plan with 1-3 focused tasks
+- Quick tasks should be atomic and self-contained
+- No research phase
+${FULL_MODE ? '- Target ~40% context usage (structured for verification)' : '- Target ~30% context usage (simple, focused)'}
+${FULL_MODE ? '- Each task MUST have files, action, convergence.criteria, implementation fields' : ''}
+</constraints>
+
+<output>
+Write plan to: ${QUICK_DIR}/plan.json
+Write tasks to: ${QUICK_DIR}/.task/TASK-{NNN}.json
+Return: ## PLANNING COMPLETE with plan path
+</output>
+",
+  subagent_type="workflow-planner",
+  description="Quick plan: ${DESCRIPTION}"
+)
+```
+
+After planner returns:
+1. Verify plan.json exists at `${QUICK_DIR}/plan.json`
+2. Update index.json plan fields
+3. Report: "Plan created: ${QUICK_DIR}/plan.json"
+
+If plan not found: "Planner failed to create plan.json"
+
+---
+
+### Step 6: Plan Checker (only when $FULL_MODE)
+
+**Plan-checker loop:**
+
+Skip entirely if NOT $FULL_MODE.
+
+```
+------------------------------------------------------------
+  WORKFLOW > CHECKING PLAN
+------------------------------------------------------------
+Spawning plan checker...
+```
+
+```
+Task(
+  prompt="
+Verify quick task plan.
+
+Read: ${QUICK_DIR}/plan.json and ${QUICK_DIR}/.task/TASK-*.json
+
+Check dimensions:
+- Requirement coverage: Does the plan address the task description?
+- Task completeness: Do tasks have files, action, convergence.criteria, implementation?
+- Scope sanity: Appropriately sized for quick task (1-3 tasks)?
+${DISCUSS_MODE ? '- Context compliance: Does plan honor decisions from context.md?' : ''}
+
+Return one of:
+- ## VERIFICATION PASSED
+- ## ISSUES FOUND -- structured issue list
+",
+  subagent_type="workflow-plan-checker",
+  description="Check quick plan: ${DESCRIPTION}"
+)
+```
+
+**Handle checker return:**
+
+- **VERIFICATION PASSED:** Continue to Step 7.
+- **ISSUES FOUND:** Enter revision loop.
+
+**Revision loop (max 2 iterations):**
+
+If iteration_count < 2:
+- Display: "Sending back to planner for revision... (iteration {N}/2)"
+- Spawn planner with revision context + checker issues
+- Re-check with checker
+- Increment iteration_count
+
+If iteration_count >= 2:
+- Display: "Max iterations reached. {N} issues remain."
+- Offer: 1) Force proceed, 2) Abort
+
+---
+
+### Step 7: Spawn Executor
+
+**Spawn workflow-executor:**
+
+```
+Task(
+  prompt="
+Execute quick task.
+
+Read:
+- ${QUICK_DIR}/plan.json (Plan)
+- ${QUICK_DIR}/.task/TASK-*.json (Tasks)
+- .workflow/state.json (Project state)
+- ./CLAUDE.md (Project instructions, if exists)
+
+Constraints:
+- Execute all tasks in the plan
+- Commit each task atomically
+- Create summary for each task at: ${QUICK_DIR}/.summaries/TASK-{NNN}-summary.md
+",
+  subagent_type="workflow-executor",
+  description="Execute: ${DESCRIPTION}"
+)
+```
+
+After executor returns:
+1. Verify summaries exist
+2. Update index.json execution fields
+3. Report completion status
+
+---
+
+### Step 8: Verification (only when $FULL_MODE)
+
+**Post-execution verification:**
+
+Skip entirely if NOT $FULL_MODE.
+
+```
+------------------------------------------------------------
+  WORKFLOW > VERIFYING RESULTS
+------------------------------------------------------------
+Spawning verifier...
+```
+
+```
+Task(
+  prompt="
+Verify quick task goal achievement.
+Task directory: ${QUICK_DIR}
+Task goal: ${DESCRIPTION}
+
+Read: ${QUICK_DIR}/plan.json and ${QUICK_DIR}/.summaries/
+
+Check plan objectives against actual codebase.
+Write verification result to: ${QUICK_DIR}/verification.json
+",
+  subagent_type="workflow-verifier",
+  description="Verify: ${DESCRIPTION}"
+)
+```
+
+Read verification result:
+| Status | Action |
+|--------|--------|
+| passed | Store "Verified", continue |
+| gaps_found | Display gaps, offer: 1) Re-run executor, 2) Accept as-is |
+
+---
+
+### Step 9: Update State
+
+**Update state.json:**
+
+Read state.json. Add quick task to accumulated_context or quick_tasks array.
+
+Record:
+```json
+{
+  "id": "quick-{slug}-{date}",
+  "description": "{$DESCRIPTION}",
+  "completed_at": "{ISO timestamp}",
+  "directory": "{$QUICK_DIR}",
+  "verified": {$FULL_MODE ? verification_status : "skipped"}
+}
+```
+
+Update last_updated timestamp.
+
+---
+
+### Step 10: Commit and Complete
+
+**Final commit and completion:**
+
+Update index.json status to "completed".
+
+Commit quick task artifacts:
+```bash
+git add "${QUICK_DIR}/" .workflow/state.json
+git commit -m "quick({slug}): ${DESCRIPTION}"
+```
+
+Display completion:
+
+If $FULL_MODE:
+```
+------------------------------------------------------------
+  WORKFLOW > QUICK TASK COMPLETE (FULL MODE)
+------------------------------------------------------------
+
+Quick Task: {$DESCRIPTION}
+
+Summary: ${QUICK_DIR}/.summaries/
+Verification: ${QUICK_DIR}/verification.json ({status})
+Directory: ${QUICK_DIR}
+
+------------------------------------------------------------
+Ready for next task: /workflow:quick
+```
+
+If NOT $FULL_MODE:
+```
+------------------------------------------------------------
+  WORKFLOW > QUICK TASK COMPLETE
+------------------------------------------------------------
+
+Quick Task: {$DESCRIPTION}
+
+Summary: ${QUICK_DIR}/.summaries/
+Directory: ${QUICK_DIR}
+
+------------------------------------------------------------
+Ready for next task: /workflow:quick
+```
+
+---
+
+## Success Criteria
+
+- [ ] --full and --discuss flags parsed from arguments when present
+- [ ] Flags are composable (--discuss --full works)
+- [ ] User provides task description (prompted if missing)
+- [ ] Project validated (state.json exists)
+- [ ] Scratch directory created at .workflow/scratch/quick-{slug}-{date}/
+- [ ] index.json created in scratch dir
+- [ ] (--discuss) Gray areas identified, decisions captured in context.md
+- [ ] (--discuss) context.md honors "All clear" skip and "You decide" discretion
+- [ ] plan.json + .task/TASK-*.json created by planner
+- [ ] (--full) Plan checker validates plan, revision loop capped at 2
+- [ ] .summaries/TASK-*-summary.md created by executor
+- [ ] (--full) verification.json created by verifier
+- [ ] state.json updated with quick task record
+- [ ] Artifacts committed
+- [ ] index.json status set to "completed"