conductor-implement

<user_request> $ARGUMENTS </user_request>

<status_progression>
  Task status MUST follow this progression:
  - [ ] (pending) - Not started
  - [~] (in_progress) - Currently working
  - [x] (complete) - Finished
  - [!] (blocked) - Blocked by issue

  Only ONE task can be [~] at a time.
</status_progression>

<tdd_workflow>
  Follow Test-Driven Development for each task:

  **Red Phase:**
  1. Create test file for the feature
  2. Write tests defining expected behavior
  3. Run tests - confirm they FAIL
  4. Do NOT proceed until tests fail

  **Green Phase:**
  1. Write MINIMUM code to pass tests
  2. Run tests - confirm they PASS
  3. No refactoring yet

  **Refactor Phase:**
  1. Improve code clarity and performance
  2. Remove duplication
  3. Run tests - confirm they still PASS
</tdd_workflow>

<git_commit_protocol>
  After completing each task:
  1. Stage relevant changes
  2. Commit with proper format:
     ```
     <type>(<scope>): <description>

     - Detail 1
     - Detail 2

     Task: {phase}.{task}
     ```
  3. Attach git note with task summary:
     ```bash
     git notes add -m "Task: {phase}.{task} - {title}

     Summary: {what was accomplished}

     Files Changed:
     - {file1}: {description}

     Why: {business reason}" $(git log -1 --format="%H")
     ```
  4. Update metadata.json with commit SHA
</git_commit_protocol>

<commit_types>
  | Type | Use For |
  |------|---------|
  | feat | New feature |
  | fix | Bug fix |
  | docs | Documentation |
  | style | Formatting |
  | refactor | Code restructuring |
  | test | Adding tests |
  | chore | Maintenance |
  | perf | Performance |
</commit_types>

<workflow_adherence>
  ALWAYS follow procedures in conductor/workflow.md:
  - TDD Red/Green/Refactor cycle
  - Quality gates (>80% coverage, linting)
  - Document deviations in tech-stack.md
  - Phase Completion Protocol at phase end
</workflow_adherence>

<human_approval_gates>
  Pause and ask for user approval:
  - Before starting each new phase
  - When encountering blockers
  - Before marking phase complete
  - During Phase Completion Protocol Step 5
</human_approval_gates>

</critical_constraints>

<core_principles> Focus on exactly one task. Complete it fully before moving to next. No partial implementations.

<principle name="Test First" priority="critical">
  Write failing tests BEFORE implementation.
  This is the Red phase of TDD.
  Never skip this step.
</principle>

<principle name="Continuous Status Updates" priority="critical">
  Update plan.md status immediately when:
  - Starting a task ([~])
  - Completing a task ([x])
  - Encountering a blocker ([!] with note)
</principle>

<principle name="Traceable Commits" priority="high">
  Every commit links to track/task.
  Commit messages follow type convention.
  Git notes provide audit trail.
</principle>

</core_principles>