feature-implementer

Automate feature implementation workflows from design to validation.

5|10|Updated Jan 8, 2026

Search Tags:#testing #documentation #task-management #automate #design-docs #feature-implementation

Ready to run

npx skills add https://github.com/chaitin/MonkeyCodeOfficialPlugins --skill feature-implementer-chaitin

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: feature-implementer
Source: https://github.com/chaitin/MonkeyCodeOfficialPlugins/tree/main/skills/feature-implementer
Command: npx skills add https://github.com/chaitin/MonkeyCodeOfficialPlugins --skill feature-implementer-chaitin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the end-to-end feature implementation workflow from design to validation, reducing manual orchestration and human error.

Core Features & Use Cases

Orchestrates reading .monkeycode/specs/{FEATURE_NAME}/design.md, tasklist.md, and requirements.md, and consults project docs under .monkeycode/docs/ (INDEX.md, ARCHITECTURE.md, INTERFACES.md, DEVELOPER_GUIDE.md) to guide implementation.
Enforces a task-by-task execution discipline: read specs, implement code, write tests, update tasklist, and optionally sync documentation.
Supports feature-name scoped workflows by substituting {FEATURE_NAME} with the actual feature during execution.

Quick Start

Tell me the feature name and an optional task ID to begin the implementation workflow.

Frequently Asked Questions about feature-implementer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate feature implementation from design docs to testing?▼

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.

How do I use design docs and requirements to generate working code?▼

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.

Can I sync documentation updates automatically during feature implementation?▼

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.

What is the best way to enforce task-by-task execution discipline in software engineering?▼

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.

Do I need to prepare specific spec files before starting feature implementation?▼

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.

Why does feature implementation fail when project docs are not consulted?▼

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.