Verified:GitHub

implement

Implements work items from a PRD or issues using TDD and code review.

Updated Jul 3, 2026

Search Tags:#testing #tdd #code review #commit #prd #implement #typechecking

One-click install

npx skills add https://github.com/alex-jordan547/agent-setup --skill implement-alex-jordan547

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/alex-jordan547/agent-setup/tree/main/archive/2026-09-10/implement
Command: npx skills add https://github.com/alex-jordan547/agent-setup --skill implement-alex-jordan547

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a PRD or a set of issues into committed, tested code requires a disciplined workflow that is easy to skip under time pressure. This Skill enforces a consistent implementation loop so work is built test-first, typechecked, reviewed, and committed without missing steps. ## Core Features & Use Cases - PRD/Issue-Driven Implementation: Reads the work described in a PRD or issues and implements it directly. - Test-Driven Development: Applies TDD at pre-agreed seams, runs typechecking and single test files regularly, and runs the full test suite once at the end. - Review and Commit: Triggers a code review of the finished work and commits it to the current branch. - Use Case: You have a PRD describing a new API endpoint. Invoke this Skill to implement it with TDD, verify types and tests, review the diff, and land the commit on your feature branch. ## Quick Start Implement the work described in this PRD using TDD, then review and commit it to the current branch.

Frequently Asked Questions about implement

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

FAQPage Schema

How do I implement a feature from a PRD with an AI coding agent?▼

Provide the PRD or issue set and invoke the implement workflow. The agent builds the work using TDD at pre-agreed seams, runs typechecking and tests along the way, reviews the result, and commits it to the current branch.

How to apply test-driven development when implementing issues?▼

Apply TDD at pre-agreed seams rather than everywhere, writing tests before the implementation at those boundaries. Run single test files regularly during development and the full test suite once at the end.

Does this workflow run the full test suite on every change?▼

No. It runs typechecking and individual test files regularly during development, and executes the full test suite only once at the end before review and commit.

When should I not use a PRD-driven implementation workflow?▼

Avoid it for exploratory spikes or throwaway prototypes where TDD and formal review add overhead without value. It fits best when requirements are already defined in a PRD or issues.