implement

Execute test-driven development with failing tests, minimal implementation, and verified passing tests.

36|3|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/dfrysinger/qrspi-plus --skill implement-dfrysinger
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/dfrysinger/qrspi-plus/tree/main/skills/implement
Command: npx skills add https://github.com/dfrysinger/qrspi-plus --skill implement-dfrysinger

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforces disciplined test-driven development and per-task implementation workflows so production code is never introduced without a failing test first, while coordinating automated and human reviews to ensure correctness and safety.

Core Features & Use Cases

  • Per-task TDD Orchestration: Spawn an implementer subagent for each task to write failing tests, implement minimal code to pass them, and perform self-review before committing.
  • Reviewer Gatekeeping: Run spec, code-quality, silent-failure, and security reviewers (always) and optional thoroughness reviewers (deep mode) with clear execution order and gating rules.
  • Quick Fix and Full Pipeline Modes: Support quick-fix single-task flows and full worktree-based feature flows with explicit artifact gating based on pipeline type.
  • Artifact Tracking & Reporting: Produce per-task review artifacts and status codes (DONE, DONE_WITH_CONCERNS, NEEDS_CONTEXT, BLOCKED) and enforce review/fix loops with limits.

Quick Start

Orchestrate TDD for a dispatched task by running the implement skill to spawn an implementer subagent that writes a failing test, implements the minimal fix until tests pass, and dispatches configured reviewers.

Frequently Asked Questions about implement

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

FAQPage Schema
How do I enforce test-driven development for individual coding tasks?▼

To enforce test-driven development, this skill spawns an implementer subagent for each task to write a failing test first, implement minimal code to pass it, and run automated reviewers before committing.

What is the best way to automate code review and security checks in a TDD workflow?▼

Automating code review in a TDD workflow is handled by running spec, code-quality, silent-failure, and security reviewers with configurable thoroughness and gating rules after the initial implementation passes its tests.

Can I use a worktree-based pipeline for multi-file features and a quick-fix mode for single-file bugs?▼

Yes, you can use worktree-driven full pipeline mode for multi-file feature implementations and quick-fix mode for single-file bug fixes, with explicit artifact gating applied based on the pipeline type.

How do review gates handle failing tests or blocked implementation tasks?▼

Review gates enforce review and fix loops with limits, producing per-task status codes like DONE, DONE_WITH_CONCERNS, NEEDS_CONTEXT, or BLOCKED to track the outcome of the implementation workflow.

What is deep thoroughness mode for code reviews?▼

Deep thoroughness mode is an optional configuration that launches additional thoroughness reviewers alongside the standard spec, code-quality, silent-failure, and security reviewers to enforce stricter review gating.