One-click install
npx skills add https://github.com/cloudofgeorge/AI-hands-Engineer --skill implement-cloudofgeorge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/cloudofgeorge/AI-hands-Engineer/tree/main/skills/engineering/implement
Command: npx skills add https://github.com/cloudofgeorge/AI-hands-Engineer --skill implement-cloudofgeorge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a spec or set of tickets into committed, reviewed code involves many small decisions about testing, verification, and review. This Skill provides a disciplined implementation workflow so the work is executed consistently rather than ad hoc. ## Core Features & Use Cases - Spec-Driven Implementation: Executes the work described in a user-provided spec or ticket set. - Test-Driven Workflow: Applies TDD at pre-agreed seams, runs typechecking and single test files regularly, and runs the full test suite once at the end. - Built-In Review and Commit: Finishes by running a code review pass and committing the work to the current branch. - Use Case: You have a ticket describing a new API endpoint. Invoke this Skill to implement it with tests at the agreed boundaries, verify with typechecks and the test suite, review the diff, and commit the result. ## Quick Start Implement the work described in this spec using TDD at the agreed seams, then review and commit it.

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 spec or ticket with an AI agent?

Provide the spec or tickets and invoke this Skill. It implements the described work, applies TDD at pre-agreed seams, runs typechecking and tests, reviews the result, and commits to the current branch.

How does this Skill use test-driven development?

It applies TDD where possible at pre-agreed seams, meaning test-first development happens at boundaries you defined beforehand rather than everywhere indiscriminately. Typechecking and single test files run regularly during the work.

When are tests and typechecks run during implementation?

Typechecking and individual test files run regularly throughout the implementation. The full test suite runs once at the end, after the work is complete, to confirm nothing regressed.

Does the implementation get reviewed before committing?

Yes. After implementation finishes, the Skill runs a code review pass over the work using the companion code review workflow, and only then commits the changes to the current branch.

What inputs does this implementation workflow require?

It requires a spec or set of tickets describing the work, plus a checked-out branch to commit to. It also assumes the companion TDD and code review skills are available in the environment.