spec-implement

Convert approved specification documents into reviewer-verified code changes with tasks.md tracking.

4|Updated Feb 9, 2021

Search Tags:#git workflow #dependency management #task queue #spec implementation #requirements tracing #code review orchestration

Ready to run

npx skills add https://github.com/breengles/poor-man-OS-setup --skill spec-implement-breengles

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-implement
Source: https://github.com/breengles/poor-man-OS-setup/tree/main/.claude/skills/spec-implement
Command: npx skills add https://github.com/breengles/poor-man-OS-setup --skill spec-implement-breengles

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of turning an approved engineering spec into correct, reviewed, and tracked code changes without losing context or mixing responsibilities.

Core Features & Use Cases

Task-by-task implementation orchestration: Reads requirements.md, design.md, tasks.md, and optional research.md and constitution.md, then runs tasks in a controlled queue.
Quality-gated review loop: Dispatches an implementer and then a reviewer for each batch, updating tasks.md only after an APPROVED verdict.
Resilient retry and escalation: Handles REJECTED outcomes with fix rounds and escalates to a stronger model after repeated failures, or blocks tasks when necessary.
Dependency-aware execution: Skips Done tasks, respects Blocked tasks, and enforces _Depends_ prerequisites.

Quick Start

Use the spec-implement skill to implement the approved feature "my-feature" tasks 2.1 and 2.3 in order by telling the agent: implement my-feature 2.1 2.3.

Frequently Asked Questions about spec-implement

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

FAQPage Schema

How do I implement approved specification documents into tracked code changes?▼

To implement approved specification documents, an orchestrator converts requirements.md, design.md, and tasks.md into incremental code changes, dispatching independent implementer and reviewer subagents to verify quality before updating task tracking.

How does dependency-aware task queue execution work for spec implementation?▼

Dependency-aware task queue execution skips Done tasks, respects Blocked tasks, and enforces _Depends_ prerequisites, ensuring spec implementation runs in the correct order without violating boundary scoping or requirement tracing.

What happens when a code review verdict is REJECTED during spec implementation?▼

When a code review verdict is REJECTED during spec implementation, the system initiates resilient fix rounds and escalates to a stronger model after repeated failures, blocking tasks when necessary until an APPROVED verdict is reached.

Can I run all pending tasks from a tasks.md file in a single batch?▼

Yes, you can run all pending tasks from tasks.md in an all-pending mode with dependency checks, or target specific task selections like tasks 2.1 and 2.3 to control the spec implementation queue.

Do I need an orchestrator-only workflow to enforce spec implementation boundaries?▼

Yes, an orchestrator-only workflow enforces boundary scoping and batched review/commit logic, dispatching independent implementer and reviewer subagents while gating blocked and done state transitions strictly by APPROVED verdicts.