Implementation Process

Act as expert implementation orchestrator coordinating task execution across agents. Dispatch executor and reviewer agents per task — managing plan reading, task extraction, agent invocation, git operations, and progress tracking.

Purpose in the Workflow

Follows planning. Execute the plan task by task — an executor implements via strict TDD, a reviewer independently verifies.

What This Skill Needs

• Plan content (required) - Phases, tasks, and acceptance criteria to execute
• Plan format (required) - How to parse tasks (from manifest)
• Specification content (required) - The specification from the prior phase, for context when task rationale is unclear
• Environment setup (optional) - First-time setup instructions

Resuming After Context Refresh

Context refresh (compaction) summarizes the conversation, losing procedural detail. When you detect a context refresh has occurred — the conversation feels abruptly shorter, you lack memory of recent steps, or a summary precedes this message — follow this recovery protocol:

1. Re-read this skill file completely. Do not rely on your summary of it. The full process, steps, and rules must be reloaded.
2. Check task progress in the plan — use the plan adapter's instructions to read the plan's current state. Check manifest state for additional context.
3. Check gate modes and progress via manifest CLI:
   bashCopy

   node .claude/skills/workflow-manifest/scripts/manifest.cjs get {work_unit}.implementation.{topic}
   

   Check task_gate_mode, fix_gate_mode, analysis_gate_mode, fix_attempts, and analysis_cycle — if gates are auto, the user previously opted out. If fix_attempts > 0, you're mid-fix-loop for the current task. If analysis_cycle > 0, you've completed analysis cycles — check for findings files on disk (analysis-*-c{cycle-number}.md in the implementation directory) to determine mid-analysis state.
4. Check git state. Run git status and git log --oneline -10 to see recent commits. Commit messages follow a conventional pattern that reveals what was completed.
5. Announce your position to the user before continuing: what step you believe you're at, what's been completed, and what comes next. Wait for confirmation.

Do not guess at progress or continue from memory. The files on disk and git history are authoritative — your recollection is not.

Hard Rules

1. No autonomous decisions on spec deviations — when the executor reports a blocker or spec deviation, present to user and STOP. Never resolve on the user's behalf.
2. All git operations are the orchestrator's responsibility — agents never commit, stage, or interact with git.

Output Formatting

When announcing a new step, output ── ── ── ── ── on its own line before the step heading.

Step 0: Resume Detection

Check if an implementation entry exists in the manifest:

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

If implementation entry does not exist

→ Proceed to Step 1.

If implementation entry exists

Output the next fenced block as a code block:

Found existing implementation for "{topic:(titlecase)}". Resuming from previous session.

Reset gate modes and counters via manifest CLI (fresh session = fresh gates/cycles):

node .claude/skills/workflow-manifest/scripts/manifest.cjs set {work_unit}.implementation.{topic} task_gate_mode gated
node .claude/skills/workflow-manifest/scripts/manifest.cjs set {work_unit}.implementation.{topic} fix_gate_mode gated
node .claude/skills/workflow-manifest/scripts/manifest.cjs set {work_unit}.implementation.{topic} analysis_gate_mode gated
node .claude/skills/workflow-manifest/scripts/manifest.cjs set {work_unit}.implementation.{topic} fix_attempts 0
node .claude/skills/workflow-manifest/scripts/manifest.cjs set {work_unit}.implementation.{topic} analysis_cycle 0

→ Proceed to Step 1.

Step 1: Environment Setup

Load environment-setup.md and follow its instructions as written.

→ Proceed to Step 2.

Step 2: Read Plan + Load Plan Adapter

Load load-plan-adapter.md and follow its instructions as written.

→ Proceed to Step 3.

Step 3: Initialize Implementation Tracking

Load initialize-tracking.md and follow its instructions as written.

→ Proceed to Step 4.

Step 4: Project Skills Discovery

Load project-skills-discovery.md and follow its instructions as written.

→ Proceed to Step 5.

Step 5: Linter Discovery

Load linter-setup.md and follow its instructions as written.

→ Proceed to Step 6.

Step 6: Task Loop

Load task-loop.md and follow its instructions as written.

After the loop completes:

If the task loop exited early (user chose stop)

→ Proceed to Step 8.

Otherwise

CRITICAL: This routing applies on every task loop completion — including after returning from Step 7 with analysis-created tasks. Step 6 and Step 7 form a mandatory cycle: tasks execute → analysis runs → new tasks may be created → tasks execute again → analysis runs again. Never skip Step 7 after a task loop completes.

→ Proceed to Step 7.

Step 7: Analysis Loop

Load analysis-loop.md and follow its instructions as written.

If new tasks were created in the plan

→ Return to Step 6.

If no tasks were created

→ Proceed to Step 8.

Step 8: Compliance Self-Check

Load compliance-check.md and follow its instructions as written.

→ Proceed to Step 9.

Step 9: Mark Implementation Complete

Load conclude-implementation.md and follow its instructions as written.