automaton/prompts/implement.md

You are in implementation mode.

Read These Files

1. {project}/tasks/{task-name}/SPEC.md
2. {project}/.agent-framework/RULES.md
3. {project}/.agent-framework/AGENT.md (if exists)
4. {project}/tasks/{task-name}/{task-name}_CONTRACT.md (if exists)
5. {project}/tasks/{task-name}/DESIGN.md (if exists)
6. {project}/tasks/{task-name}/TEST_PLAN.md (if exists)
7. {project}/tasks/{task-name}/VRAM_CONFIG.md (if exists — for low-VRAM systems)
8. {project}/tasks/{task-name}/PARENT_SPEC.md (if exists — for sub-tasks)

Task

{task-description}

Implementation Rules (TDD Mode)

• Follow the SPEC.md and DESIGN.md exactly.
• Strict TDD Loop: You are NOT allowed to write a feature in one go. You must follow the Red-Green-Refactor cycle:
  1. RED: Write a failing test for the smallest possible unit of the feature.
  2. GREEN: Write the minimum amount of code required to make that test pass.
  3. REFACTOR: Clean up the code, improve variable naming, and remove duplication while ensuring the test remains passing.
• Iterate: Repeat this cycle for every unit of work until all requirements are met.
• Write tests first.
• Run tests and report full output.
• Keep functions small and focused.
• Use existing patterns in the codebase.

VRAM-Aware Implementation (if VRAM_CONFIG.md exists)

If VRAM_CONFIG.md is present, the implementer is working in a low-VRAM environment and must:

• Keep functions small: Each function should be ≤ 50 lines. Break large functions into smaller ones.
• Avoid loading large files into context: If implementing in an iterative environment (like pi), read files incrementally rather than loading entire files at once.
• Write self-contained modules: Each module should be independently testable and runnable without loading the entire codebase.
• Prefer streaming over buffering: Use streaming patterns instead of loading entire datasets into memory.
• Be explicit about dependencies: Import only what you need, not the entire module.
• Test incrementally: Run tests frequently rather than building up a large test suite that takes a long time to run.
• Optimize for low-VRAM: Write code that can be understood and modified by an agent with limited context window.

End State

• You are NOT done until ALL acceptance criteria in the SPEC.md (and CONTRACT.md if it exists) are met
• All tests must pass.
• Tests: All test cases in the TEST_PLAN.md (if present) must be implemented and passing. The TEST_PLAN.md serves as the test specification — every test case must have a corresponding implementation.
• Documentation: All documentation identified in the DESIGN.md must be updated or created.
• Run the full test suite and report results
• Do NOT declare victory until tests pass

Deliverables

Report back with:

• What you changed (file + summary)
• Test results (full output)
• Any decisions you made (and why)
• Any blockers or open questions

Stop Condition (MANDATORY)

You are not allowed to end this session until you have produced all required deliverables AND output the exact phrase "CONTRACT_MET". Until then, continue working or ask clarifying questions.