implementer

Execute feature tasks sequentially with live documentation and git commits.

Updated Feb 5, 2026
One-click install
npx skills add https://github.com/edumesones/azure--demo --skill implementer-edumesones
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implementer
Source: https://github.com/edumesones/azure--demo/tree/main/.claude/skills/implementer
Command: npx skills add https://github.com/edumesones/azure--demo --skill implementer-edumesones

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured framework to implement features by guiding task execution, live documentation updates, and context logging, reducing drift and improving traceability across teams.

Core Features & Use Cases

  • Task-by-task feature execution: identifies next uncompleted task, updates status, and progresses work in small increments.
  • Live documentation updates: automatically records decisions, blockers, and session logs as work proceeds.
  • Git-aligned workflow: enforces feature branch creation, commits after each task, and checkpoint updates for progress tracking.

Quick Start

Start by preparing a feature folder with a spec.md, design.md, and a tasks.md; then invoke the skill to begin executing the first pending task and update context automatically.

Frequently Asked Questions about implementer

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

FAQPage Schema
How do I execute feature tasks while maintaining live documentation updates?

Feature implementation with live docs works by orchestrating task execution against a feature folder containing spec.md, design.md, and tasks.md. It performs task-by-task execution, updates task statuses, and logs session context in real-time to reduce drift.

What is the best way to track blockers and session logs during iterative feature implementation?

Tracking blockers during iterative feature implementation is handled by maintaining a session_log and blockers within your feature folder. The workflow enforces recording decisions and issues as work proceeds, ensuring reproducibility and traceability across teams.

How do I set up a git workflow for task-by-task feature implementation?

To set up a git workflow for task-by-task feature implementation, prepare a feature folder with spec.md, design.md, and tasks.md. The process enforces creating a dedicated git feature branch, committing after each task, and pushing checkpoints for progress tracking.

Do I need spec.md and design.md files to start executing feature tasks?

Yes, you need spec.md, design.md, and tasks.md files prepared in a feature folder to start executing feature tasks. The workflow operates on these files to identify the next uncompleted task, update statuses, and progress work in small increments.

Can I use context logging to ensure reproducibility across multiple feature branches?

Yes, context logging ensures reproducibility across multiple feature branches by automatically recording decisions, blockers, and session logs. It enforces updating tasks.md statuses and pushes git checkpoints after each task completion for traceability.

Why does my feature implementation drift from the original design specifications?

Feature implementation drifts from design specifications when live documentation is not updated during execution. Enforcing real-time updates to tasks.md statuses and maintaining a session_log as work proceeds provides a structured framework to reduce drift and improve traceability.