🎯 Workflow Manager active. Checking project state...

You are executing the {skill_name} skill.

## Your Task
{Brief description of what to do}

## Files to Read
Read these files before starting work:
- Skill instructions: {path to skill's SKILL.md}
- Spec: {spec_path} (if applicable)
- Spec I/O reference: {path to shared/spec-io.md} (if skill uses specs)
- GitHub ops reference: {path to shared/github-ops.md} (if skill uses GitHub)
- Project context: {path to project AGENTS.md}

## Inputs
- Spec path: {spec_path}
- Issue: #{issue_number} (if applicable)

## Constraints
- Read the skill instructions first, then follow them exactly
- Do not add features beyond the spec
- Fail loudly if something is wrong
- Write all outputs to files (spec updates, test files, code)
- Read the Security Considerations section of the spec. Follow `shared/security-lens.md` patterns for any auth/RLS/edge function/input validation work
- Before reporting done, re-read the acceptance criteria from the spec
- For each criterion, assess: ✅ satisfied / ⚠️ partially satisfied or unsure / ❌ not satisfied
- Include a 🔒 Security line in your satisfaction assessment (see `shared/security-lens.md` Review-Time section)
- Be honest — flag anything you couldn't verify or are uncertain about
- When done, report: what you did, what files changed, satisfaction assessment, current artifact state

You are investigating a bug.

## Bug Context (from manager triage)
- **Issue:** #{issue_number} (or "untracked")
- **Actual behavior:** {what_happens}
- **Expected behavior:** {what_should_happen}
- **Reproduction:** {steps}
- **Started:** {when}
- **Environment:** {details}

## Files to Read
- Skill instructions: ~/.claude/skills/diagnose/SKILL.md
- Spec I/O reference: ~/.claude/skills/shared/spec-io.md
- GitHub ops: ~/.claude/skills/shared/github-ops.md
- Project context: {AGENTS.md path}

## Constraints
- Do NOT ask the user questions — all context is above
- Investigate the codebase: search for the code path, check git history, find root cause
- Write a bug spec to Documents/specs/
- Return: root cause summary, files involved, draft spec path, satisfaction assessment

📤 Dispatching: spec-review
   Input: Documents/specs/42-dark-mode-spec.md
   Reading: spec-review/SKILL.md, shared/spec-io.md

📥 spec-review complete
   Result: 3 gaps found (missing non-goals, vague criterion #4, no error states)
   Files changed: none (read-only skill)
   Next: [GATE A] Your approval needed

📥 implement-direct complete
   Files changed: QuoteForm.tsx, useQuotePrice.ts
   Satisfaction:
     ✅ Price updates on service change
     ✅ Notary fee displays separately
     ⚠️ Hourly rate message — implemented but copy may not match spec
     ✅ Total reflects all line items
     🔒 Security: RLS policies added for new table, input validated
   Next: [GATE B] Your review — 1 item flagged

Spec review complete. Here's the assessment:
{summary from spec-review sub-agent}

Your decision:
1. Approve — and choose: TDD or Direct implementation?
2. Revise — I'll update the spec based on your feedback

Implementation complete. {summary}
{satisfaction assessment with any ⚠️ flags}

Your decision:
1. Looks good — I'll update GitHub issue #{number} and proceed to QA handoff
2. Changes needed — describe what to fix

Security backlog ranked. {summary of top items}

Your decision:
1. Proceed — start fixing from the top
2. Reprioritize — tell me what to change

STEP 1: Spec exists?
  NO  → invoke /interview directly  →  STEP 2
  YES → STEP 2

STEP 2: Spec status?
  Draft    → dispatch spec-review sub-agent  →  STEP 3
  Approved → STEP 4

STEP 3: [HUMAN GATE A] Spec review complete.
  STOP. Present findings to human.
  "Approved, TDD"    → set spec status to Approved  →  STEP 4
  "Approved, Direct" → set spec status to Approved  →  Direct Path STEP 4
  "Revise"           → back to STEP 1

STEP 4: Test Plan section exists?
  NO  → dispatch plan-tests sub-agent  →  STEP 5
  YES → read Test Plan.status          →  STEP 5

STEP 5: Test Plan.status?
  Planned       → dispatch write-failing-test sub-agent  →  STEP 6
  Tests Written → STEP 6
  Passing       → STEP 7

STEP 6: dispatch implement-to-pass sub-agent  →  STEP 7

STEP 7: [HUMAN GATE B] Implementation complete.
  STOP. Human reviews PR.
  "Approved" → STEP 8
  "Changes"  → human edits  →  STEP 6

STEP 8: dispatch qa-handoff sub-agent
  DONE.

STEP 1–3: Same as TDD path.

STEP 4: dispatch implement-direct sub-agent

STEP 5: [HUMAN GATE B] Verify manually.
  STOP. Human tests the feature.
  "Looks good" → STEP 6
  "Broken"     → back to STEP 4

STEP 6: dispatch qa-handoff sub-agent
  DONE.

STEP 1: Bug triage (manager does this in-conversation)
  a. If issue number provided, read it: `gh issue view #N`
  b. Ask the human (skip any already answered by the issue):
     - What's actually happening?
     - What should happen?
     - How to reproduce?
     - When did it start?
     - Environment?
  c. Dispatch diagnose sub-agent with triage context  →  STEP 2

STEP 2: Diagnose sub-agent returns
  Review findings and draft bug spec.
  Present to human: "Here's what the investigation found: {summary}"
  Confirm spec is accurate.
  If tracked in GitHub → post diagnosis comment (with user confirmation).
  NOTE: diagnose generates a bug spec (status: Approved).
        Bug specs skip the interview/review cycle.

STEP 3: [Human chooses path]
  TDD    → dispatch plan-tests sub-agent  →  continue with TDD Feature Path STEP 5+
  Direct → dispatch implement-direct sub-agent  →  continue with Direct Feature Path STEP 5+

STEP 4: Bug tracked in GitHub?
  YES → dispatch qa-handoff sub-agent
  NO  → DONE.

STEP 1: dispatch 1-security-audit sub-agent
  Creates SECURITY_PLAN.md with findings as Pending.

STEP 2: dispatch 2-security-critique sub-agent
  Removes false positives, ranks items.

STEP 3: [HUMAN GATE C] Backlog ranked. Human reviews priorities.
  STOP. Present ranked backlog to human.
  "Looks right"    → STEP 4
  "Reprioritize"   → human edits  →  STEP 2

STEP 4: [LOOP CHECK] Pending items in ranked backlog?
  NO  → DONE. All items fixed or acknowledged.
  YES → STEP 5

STEP 5: dispatch 3-security-spec sub-agent
  Picks top Pending item. Writes failing test.

STEP 6: dispatch 4-security-fix sub-agent
  Implements fix. Marks item DONE.
  → back to STEP 4