implement

Implement work from a spec or tickets using TDD, typechecking, and code review.

Updated Jun 28, 2026
One-click install
npx skills add https://github.com/AO-HyS/aohys.com --skill implement-ao-hys
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/AO-HyS/aohys.com/tree/main/.agents/skills/implement
Command: npx skills add https://github.com/AO-HyS/aohys.com --skill implement-ao-hys

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a written spec or ticket set into committed, verified code requires disciplined sequencing: writing tests, running typechecks, executing test suites, and reviewing the result. This Skill encodes that implementation workflow so the work follows a consistent engineering process instead of ad-hoc coding. ## Core Features & Use Cases - Spec-Driven Implementation: Builds the work described by the user in a spec or set of tickets. - TDD at Agreed Seams: Applies test-driven development where possible at pre-agreed boundaries, with regular typechecking and single test file runs. - Review and Commit Flow: Runs a full test suite at the end, invokes a code review pass, and commits the work to the current branch. - Use Case: A developer has an approved ticket breakdown for a new API endpoint and wants the implementation built with tests, typechecked, reviewed, and committed on the current branch. ## Quick Start Implement the work described in this spec using TDD, run the full test suite, review the changes, and commit them 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 spec or tickets with AI?▼

Provide the spec or ticket set and invoke the implement workflow. It builds the described work using test-driven development at pre-agreed seams, runs typechecking and tests regularly, then reviews and commits the result to the current branch.

How does test-driven development fit into the implementation workflow?▼

TDD is applied where possible at pre-agreed seams, meaning tests are written at the boundaries agreed upon before implementation. Single test files run regularly during development, and the full test suite runs once at the end.

Does the implement skill run code review automatically?▼

Yes, after implementation and the full test suite pass, the workflow invokes a separate code review step on the completed work. The changes are then committed to the current branch.

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

Avoid it for exploratory prototyping or spikes where requirements are undefined, since the workflow expects a concrete spec or tickets. It also assumes an existing branch and test setup, so greenfield repos may need scaffolding first.