implement

Implement code changes from specs or tickets using test-driven development.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/sndrgrdn/skills --skill implement-sndrgrdn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/sndrgrdn/skills/tree/main/implement
Command: npx skills add https://github.com/sndrgrdn/skills --skill implement-sndrgrdn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a written spec or set of tickets into working, tested code requires discipline: writing tests first, running typechecks, and reviewing the result. This Skill structures that entire implementation workflow so nothing gets skipped. ## Core Features & Use Cases - Spec-Driven Implementation: Builds the work described in a spec or ticket set, following test-driven development at pre-agreed seams. - Continuous Verification: Runs typechecking and single test files regularly, then the full test suite once at the end. - Built-In Review and Commit: Finishes with a code review pass and commits the work to the current branch. - Use Case: You have a ticket describing a new API endpoint. Invoke this Skill to implement it with TDD, verify types and tests, review the diff, and commit the finished change. ## Quick Start Implement the work described in the current spec or tickets using test-driven development, 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 using TDD?▼

Start from the spec or tickets, write tests first at pre-agreed seams, then implement until they pass. Run typechecking and single test files regularly, and execute the full test suite once at the end before committing.

How to turn tickets into working code with an AI assistant?▼

Provide the spec or ticket set and invoke the implement workflow. It builds the described work with test-driven development, verifies types and tests, runs a code review, and commits the result to the current branch.

When should the full test suite run during implementation?▼

Run single test files and typechecking regularly during development, but execute the full test suite only once at the end. This keeps iteration fast while still validating the complete codebase before committing.

Does the implement workflow include code review?▼

Yes, after implementation and testing are complete, the workflow runs a code review pass over the work. Only after that review does it commit the changes to the current branch.

What are the limitations of spec-driven implementation?▼

The output quality depends on the clarity of the spec or tickets and on agreed testing seams. Vague requirements or missing test coverage boundaries can lead to incomplete or misaligned implementations.