implementer

Coordinate two-checkpoint feature implementation from approved spec and plan artifacts.

1|Updated May 3, 2026
One-click install
npx skills add https://github.com/gaabscps/ai-squad --skill implementer-gaabscps
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implementer
Source: https://github.com/gaabscps/ai-squad/tree/main/squads/sdd/skills/implementer
Command: npx skills add https://github.com/gaabscps/ai-squad --skill implementer-gaabscps

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates end-to-end feature implementation within a single session, preventing drift from approved specs and eliminating fragmented handoffs.

Core Features & Use Cases

  • Two fixed checkpoints: plan approval and final seal enforce discipline, visibility, and auditable decisions.
  • Curated context and reuse: loads artifacts (spec.md, plan.md, tasks.md, CLAUDE.md) to keep implementation focused and context-consistent.
  • Strict scope control: tracks decisions, evidence, and approved write scope in session.yml to guard against scope creep.
  • Human-in-the-loop safeguards: combines automated tooling with human reviews at checkpoints to balance speed and correctness.

Quick Start

Invoke /implementer FEAT-NNN in your session to begin implementing an approved feature, and use /implementer FEAT-NNN --resume to continue from a checkpoint.

Frequently Asked Questions about implementer

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

FAQPage Schema
How do I automate end-to-end feature implementation while preventing drift from an approved spec?

You can resume an interrupted feature implementation session by invoking the command with the --resume flag, which restores your progress from the last checkpoint using the tracked state stored in session.yml.

What's the best way to enforce human-in-the-loop quality control during a feature implementation session?

Human-in-the-loop quality control is enforced through two fixed checkpoints requiring explicit decisions and evidence, balancing automated tooling with human reviews to guard against scope creep before sealing the implementation.

How do I track approved write scope and decisions during feature implementation?

Approved write scope and decisions are tracked in session.yml, which logs explicit evidence and approved changes to maintain strict scope control and guard against unauthorized modifications throughout the workflow.

Do I need an approved spec and plan before starting an automated feature implementation workflow?

An approved spec and plan are required before starting, as the workflow targets sessions with existing artifacts like spec.md and plan.md to keep implementation focused, context-consistent, and strictly controlled.

Can I resume an interrupted feature implementation session from a previous checkpoint?

You can resume an interrupted feature implementation session by invoking the command with the --resume flag, which restores your progress from the last checkpoint using the tracked state stored in session.yml.