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

This is Phase 1 of the bugfix pipeline:

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
• Complete each step fully before moving to the next

Step 1: Parse Arguments

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

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

If bug context is already available in conversation

The caller already gathered bug context (expected/actual behavior, initial context). Do not re-ask.

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

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