implementer

Execute approved implementation plans through small, reviewable code changes.

36|6|Updated Feb 4, 2026
One-click install
npx skills add https://github.com/KjellKod/quest --skill implementer-kjellkod
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implementer
Source: https://github.com/KjellKod/quest/tree/main/.skills/implementer
Command: npx skills add https://github.com/KjellKod/quest --skill implementer-kjellkod

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the challenge of uncontrolled code execution by enforcing disciplined, step-by-step work on an approved implementation plan, ensuring changes are small, reviewable, and traceable.

Core Features & Use Cases

  • Step-by-step execution: Work on exactly one plan step at a time and mark progress with an ongoing/done status.
  • Traceability and mapping: Explicitly connect plan steps to code, tests, and decisions via a lightweight decision log.
  • Minimal diffs and governance: Favor small, auditable diffs and a clear decision trail to reduce risk and improve review efficiency.

Quick Start

  • Provide the approved plan with clearly numbered steps and acceptance criteria.
  • For each step, create a plan entry in the required format, run the step, then mark it as ongoing while in progress and done when completed, including tests and ac coverage.
  • Update the Decision Log with rationale, options, and outcomes, and proceed to the next step only after review.

Frequently Asked Questions about implementer

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

FAQPage Schema
How do I execute an implementation plan with traceable steps and minimal diffs?

To execute an implementation plan with traceable steps, work on exactly one numbered step at a time, mark progress with ongoing or done status, maintain a decision log, and favor small, auditable diffs to ensure changes are reviewable.

What is the best way to enforce plan discipline during software implementation?

Plan discipline during software implementation is enforced by sequentially working through approved steps, explicitly connecting each step to code and tests via acceptance criteria, and recording rationale in a lightweight decision log before proceeding.

Can I map plan steps to code changes and track acceptance criteria coverage?

Yes, you can map plan steps to code changes and track acceptance criteria coverage by creating a plan entry for each step, running the step, and marking it done with explicit test and acceptance criteria coverage connections.

How do I maintain a decision log for traceability during step-by-step coding?

To maintain a decision log for traceability during step-by-step coding, update the log with the rationale, options, and outcomes for each plan step before moving to the next one after review.

Do I need an approved implementation plan before starting step-by-step execution?

Yes, you need an approved implementation plan with clearly numbered steps and acceptance criteria before starting step-by-step execution to ensure changes remain small, auditable, and traceable.

Why should I favor minimal diffs when implementing an approved software plan?

You should favor minimal diffs when implementing an approved software plan to reduce risk, improve review efficiency, and ensure that each sequential change remains auditable and explicitly connected to plan decisions.