implement

Plan and execute feature implementation with TDD and quality gates.

26|2|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/howells/arc --skill implement-howells
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/howells/arc/tree/main/skills/implement
Command: npx skills add https://github.com/howells/arc --skill implement-howells

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams plan and execute feature implementations with Test-Driven Development (TDD) and continuous quality checks, ensuring reliable delivery from design to production.

Core Features & Use Cases

  • Plan generation: From a design doc produced by /arc:ideate, it creates an implementation plan broken into tasks.
  • Test-First execution: Writes unit or integration tests before implementing code, then iterates until tests pass; enforces type checks and lint.
  • Quality gates & review: Includes mandatory review recommendations and automated quality gates after each task.

Quick Start

After /arc:ideate has produced a design doc, invoke the implement skill to generate and execute the implementation plan. Use it to drive task-by-task execution with tests-first, type checks, and linting, culminating in a ready-to-commit change set.

Frequently Asked Questions about implement

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

FAQPage Schema
How do I implement features using TDD from a design doc?

You can implement features using TDD by generating an implementation plan from your design doc, writing unit or integration tests before code, and running type checks and lint after each task to ensure quality.

What is tests-first development and how does it enforce quality checks?

Tests-first development is writing tests before code to validate behavior, and it enforces quality checks by running type checks and lint as mandatory gates after each task to ensure reliable delivery.

Can I generate an implementation plan without writing code first?

Yes, you can generate an implementation plan before building code. The system reads your design doc, breaks it into tasks, and optionally prompts for a design review before executing the tests-first implementation.

Do I need a design doc to start planning feature implementation?

Yes, you need a design doc to start planning. The system reads an existing design doc to create an implementation plan broken into tasks, driving task-by-task execution with tests-first discipline.

What's the best way to enforce quality gates during feature implementation?

The best way to enforce quality gates is to apply automated type checks and lint after each task, iterating until tests pass, which ensures reliable delivery from design to production.

When should I prompt for a design review before building code?

You should prompt for a design review before building code when validating the implementation plan generated from your design doc, ensuring the task breakdown aligns with quality expectations before tests-first development.