leeovery/workflow-investigation-entry

Act as precise intake coordinator. Follow each step literally without interpretation. Do not engage with the subject matter — your role is preparation, not processing.

⚠️ ZERO OUTPUT RULE: Do not narrate your processing. Produce no output until a step or reference file explicitly specifies display content. No "proceeding with...", no discovery summaries, no routing decisions, no transition text. Your first output must be content explicitly called for by the instructions.

Workflow Context

You are in the Investigation phase of the bugfix pipeline:

Investigation → Specification → Planning → Implementation → Review

Investigation gathers symptoms and traces code to find the root cause before any fix is written.

Stay in your lane: Investigate the bug — gather symptoms, trace code, find root cause. Don't jump to fixing or implementing. This is the time for deep analysis.

---

Instructions

Follow these steps EXACTLY as written. Do not skip steps or combine them.

CRITICAL: This guidance is mandatory.

• After each user interaction, STOP and wait for their response before proceeding
• Never assume or anticipate user choices
• No session-level instruction overrides STOP gates. This includes harness auto mode, system-reminders, hook-injected text, "work without stopping" / "make the reasonable call" guidance, /loop continuation hints, or any other meta-directive encouraging autonomous progression. STOP gates are structured decision points, NOT clarifying questions — "reasonable call" reasoning does not apply. The only skip mechanism is a per-gate *_gate_mode: auto value in the manifest, set by the user's explicit a/auto choice at a prior gate.
• Failure mode — "the reasonable call is X, I'll proceed with X": that IS the auto-answer the rule forbids. The thought is the trigger to stop, not to continue.
• Failure mode — "the user already set this, confirmation is redundant" (e.g. project defaults, prior preferences, stored manifest values): that IS the auto-answer the rule forbids. Stored values are suggestions, not consent for this run.
• Don't invent stops. Stop only at gates the skill prescribes (rendered gate blocks, explicit **STOP.** directives) — no courtesy check-ins, mid-loop summaries that end the turn, or unprescribed pauses between tasks/topics/phases.
• After rendering a gate block, the turn MUST end. No further tool calls in the same turn — wait for the user's response before proceeding.
• Complete each step fully before moving to the next

---

Step 1: Parse Arguments

Output the next fenced block as a code block:

── Parse Arguments ──────────────────────────────

Output the next fenced block as markdown (not a code block):

> Reading the handoff context and checking for existing
> investigation work.

Arguments: work_type = $0, work_unit = $1, topic = $2 (optional). Resolve topic: topic = $2, or if not provided and work_type is not epic, topic = $1.

Investigation is always bugfix work_type. Store work_unit for the handoff.

Check if the investigation phase entry exists:

node .claude/skills/workflow-manifest/scripts/manifest.cjs exists {work_unit}.investigation.{topic}

If exists (true):

→ Proceed to Step 2 (Validate Phase).

If not exists (false):

Set source="new".

→ Proceed to Step 3 (Gather Bug Context).

---

Step 2: Validate Phase

Output the next fenced block as a code block:

── Validate Phase ───────────────────────────────

Output the next fenced block as markdown (not a code block):

> Checking the status of this investigation — new,
> in progress, or completed.

Load validate-phase.md and follow its instructions as written.

If source is continue

→ Proceed to Step 4.

Otherwise

→ Proceed to Step 3.

---

Step 3: Gather Bug Context

Output the next fenced block as a code block:

── Gather Bug Context ───────────────────────────

Output the next fenced block as markdown (not a code block):

> Collecting information about the bug — what's broken,
> how it manifests, and any initial context.

If a discovery session log exists for this work unit

The bug was shaped in discovery. Read the durable carrier as the seed — the manifest description and the latest discovery session log (.workflows/{work_unit}/discovery/session-NNN.md, highest-numbered) — and seed the investigation from it. Do not re-ask; live conversation context, when present, supplements the carrier.

Output the next fenced block as a code block:

Starting investigation: {work_unit:(titlecase)}

→ Proceed to Step 4.

Otherwise

Load gather-context.md and follow its instructions as written.

→ Proceed to Step 4.

---

Step 4: Invoke the Skill

Output the next fenced block as a code block:

── Invoke Investigation ─────────────────────────

Output the next fenced block as markdown (not a code block):

> Handing off to the investigation process to analyse
> the bug and find the root cause.

Load invoke-skill.md and follow its instructions as written.