Workflow Implementation 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 Implementation phase — executing the plan: tests first, then code (or verification flow for quick-fix). Where Implementation sits in the pipeline depends on the work type:

Stay in your lane: Execute the plan via strict TDD (or verification workflow for quick-fix). Don't re-debate decisions from the specification or expand scope beyond the plan. The plan is your authority — when unplanned work surfaces, it grows only through the processing skill's ad hoc plan-changes route, never freelanced.

Instructions

Load framework.md and follow its instructions as written.

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.

Store work_unit for the handoff.

→ Proceed to Step 2.

Step 2: Check the Code Slot

Load code-session-gate.md with phase = implementation.

→ On return, proceed to Step 3.

Step 3: Validate Phase

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

→ On return, proceed to Step 4.

Step 4: Check Dependencies

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

→ On return, proceed to Step 5.

Step 5: Invoke the Skill

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