implement

Convert tech plans into test-first implementation pipelines with Codex-based code review.

Updated Aug 23, 2026

Search Tags:#workflow #tdd #codex #code-review #software-engineering #implement #feature-development

Ready to run

npx skills add https://github.com/fancive/claude-skills --skill implement-fancive

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/fancive/claude-skills/tree/main/skills/implement
Command: npx skills add https://github.com/fancive/claude-skills --skill implement-fancive

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides teams through a test-driven, Codex-reviewed implementation workflow, enabling reliable feature delivery from a tech plan to production-ready code.

Core Features & Use Cases

TDD-driven implementation: Enforces tests-first development and immediate feedback with Codex-based code review.
Task-driven workflow: Breaks a tech plan into actionable tasks, each validated by a Red-Green-Refactor cycle and reviewed before progression.
End-to-end governance: Provides structured phases (INPUT, TASK_BREAKDOWN, TDD_CYCLE, CODE_REVIEW, REVIEW_ACTION, NEXT_TASK) to ensure quality, traceability, and collaboration.

Quick Start

Provide a tech plan path or describe the features you want to implement to start the TDD-driven implementation workflow with Codex review.

Frequently Asked Questions about implement

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

FAQPage Schema

How do I implement a tech plan using a test-driven development workflow?▼

TDD-driven implementation converts a tech plan into a task-driven pipeline, enforcing tests-first cycles and immediate feedback. It decomposes features into actionable tasks, each validated through Red-Green-Refactor phases before progression.

What is the best way to automate code review during feature development?▼

Automated code review during feature development uses Codex to evaluate code across structured phases. After completing the TDD cycle, the implementation enters a formal review phase to ensure quality and traceability before moving to the next task.

How does a task-driven workflow handle feature decomposition from a tech plan?▼

Task-driven workflow handles feature decomposition by breaking a tech plan into isolated, actionable tasks. Each task undergoes structured phases including input intake, TDD cycles, and formal code review to maintain end-to-end governance.

Can I use TDD cycles for multiple features requiring structured planning?▼

Yes, TDD cycles apply to projects requiring structured planning across multiple features. The workflow enforces deterministic Red-Green-Refactor cycles and formal peer review, ensuring reliable feature delivery from tech plan to production-ready code.

Do I need a predefined tech plan to start a test-first implementation pipeline?▼

You need a predefined tech plan path or a description of the features you want to implement to start the test-first pipeline. This input feeds the task breakdown phase, enabling structured progression through TDD cycles and code reviews.