skills.rest
yamcodes
yamcodesCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

implement

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

1|Updated Aug 24, 2026
Search Tags:#testing#tdd#code review#spec#git commit#implement#typechecking
One-click install
npx skills add https://github.com/yamcodes/the-hat --skill implement-yamcodes
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/yamcodes/the-hat/tree/main/skills/implement
Command: npx skills add https://github.com/yamcodes/the-hat --skill implement-yamcodes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a written spec or set of tickets into working, reviewed, and committed code requires discipline across testing, typechecking, and review steps that are easy to skip under time pressure. ## Core Features & Use Cases - Spec-Driven Implementation: Executes the work described in a spec or ticket set directly on the current branch. - 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 with a code review pass and commits the completed work to the current branch. - Use Case: You have a ticket describing a new API endpoint. Invoke this Skill to implement it with tests, verify types, review the diff, and commit the result. ## Quick Start Implement the work described in the attached spec 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 spec or ticket with an AI assistant?▼

Provide the spec or tickets and invoke the implement workflow. It writes the code using TDD at pre-agreed seams, runs typechecking and tests, reviews the result, and commits the work to the current branch.

How to apply TDD when implementing tickets?▼

TDD is applied at pre-agreed seams, meaning tests are written first at the boundaries agreed with the team. Single test files run regularly during development, and the full test suite runs once at the end.

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

No. Typechecking and individual test files run regularly during implementation, while the full test suite runs only once at the end to verify the complete change before review and commit.

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

Avoid it when the work is exploratory, lacks a clear spec or tickets, or when the pre-agreed TDD seams have not been defined. The workflow assumes agreed testing boundaries and a reviewable scope of work.

Related Skills

Explore More Software Engineering Skills→
Evolutionary-LeadershipEvolutionary-Leadership

implement

Implements tickets from a spec by working the unblocked frontier with TDD and reporting.

Official
Intermediate
Chorus-AIDLCChorus-AIDLC
1.1k

pr-workflow

Automate pull request workflows with git and the GitHub CLI.

Official
Intermediate
Devsoul2026Devsoul2026
150

requesting-code-review

Automate pre-commit verification with static analysis, tests, and lint checks.

Community
Advanced
wikimediawikimedia
7

protowiki-create-prototype

Create prototype folders with index.vue under src/prototypes/ for automatic gallery publishing.

Official
Basic