implement

Implement features through test-driven development with review cycles.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates incomplete, guess-driven feature work by enforcing a complete Test-Driven Development cycle with planning, implementation, review, and final verification.

Core Features & Use Cases

  • Requirement clarification (Phase 0): Asks targeted questions until acceptance criteria and constraints are fully understood.
  • TDD-driven orchestration (Phase 1): Delegates planning, verification, parallel TDD implementation in isolated worktrees, consolidation, and review.
  • Completion with enforced guardrails (Phase 2): Commits changes only after tests, lint/build, and acceptance criteria are confirmed met.

Use case: When you describe a new feature, bugfix, or chore, this skill produces a fully implemented solution with failing tests first, then green tests, then review and integration into the main output.

Quick Start

Tell your AI: "Use implement to build the new $ARGUMENTS feature with complete TDD and review cycles."

Frequently Asked Questions about implement

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

FAQPage Schema
How does test-driven development remove ambiguity in feature implementation?

Test-driven development removes ambiguity by enforcing a strict cycle of planning, writing failing tests first, and then implementing code. This ensures requirements are clarified into acceptance criteria before any functional code is written.

What is the best way to ensure a feature is fully implemented before a git commit?

The best way to ensure a feature is ready for a git commit is to verify all tests pass, run lint and build checks, and confirm acceptance criteria are fully met. Guardrails prevent committing changes with placeholders or TODOs.

How do I break down a complex feature request into manageable subtasks?

You can break down a complex feature request by applying a structured workflow that asks targeted questions to clarify constraints, then delegates the planning into isolated worktrees for parallel test-driven implementation and consolidation.

Can I use strict TDD cycles for bugfixes and chores, or is it only for new features?

Yes, you can use strict TDD cycles for bugfixes and chores. The workflow applies to any request where requirements must be clarified, broken into tasks, implemented with tests, and merged coherently.

How do code review cycles integrate with test-driven development?

Code review integrates with test-driven development by acting as a phase after parallel implementation in isolated worktrees. A reviewer checks the consolidated output against acceptance criteria before final verification and merging.