feature-implementer

Automating feature implementation from design docs to testing requires orchestrating code writing, test creation, and tasklist updates. This skill reads specs and project docs to execute tasks sequentially, ensuring code and tests are complete before marking a task done.

Using design docs and requirements to generate working code involves parsing design.md, tasklist.md, and requirements.md files. This skill reads these specifications alongside project documentation to guide task-by-task implementation and ensure code aligns with the defined architecture.

You can sync documentation updates automatically during feature implementation. The workflow includes an optional step to synchronize project docs under .monkeycode/docs/ after writing code and tests, ensuring documentation stays current before a task is marked as complete.

The best way to enforce task-by-task execution discipline is to follow a strict workflow: read specs, implement code, write tests, and update the tasklist. This skill automates this sequence, preventing human error by ensuring no step is skipped before completion.

You need to prepare specific spec files before starting feature implementation. The workflow requires design.md, tasklist.md, and requirements.md placed under .monkeycode/specs/{FEATURE_NAME}/, and uses project docs under .monkeycode/docs/ for architectural context.

Feature implementation fails when project docs are not consulted because the code may diverge from the established architecture. This skill consults INDEX.md, ARCHITECTURE.md, and INTERFACES.md to ensure the new feature integrates correctly with the existing system design.