skills.rest
shaahy
shaahyCOMMUNITY
Explore all skills by this author →
GitHub

implement

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

Updated Aug 3, 2026
Search Tags:#tdd#code review#commit#spec#tickets#implement#typechecking
One-click install
npx skills add https://github.com/shaahy/quicknav-desktop --skill implement-shaahy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/shaahy/quicknav-desktop/tree/main/A%20%E6%95%99%E7%A8%8B%E9%9B%86%E5%90%88/Matt%20Pocock%20Skills%20%E6%8A%80%E8%83%BD%E9%80%9F%E6%9F%A5/source-snapshot/skills/engineering/implement
Command: npx skills add https://github.com/shaahy/quicknav-desktop --skill implement-shaahy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a written spec or ticket set into committed, tested code requires discipline: writing tests first, running typechecks, and reviewing the result. This Skill guides the AI through that disciplined implementation workflow so work is completed consistently rather than ad hoc. ## Core Features & Use Cases - Spec-Driven Implementation: Builds the work described in a spec or set of tickets, keeping changes aligned with agreed requirements. - 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. - Review and Commit: Finishes by invoking 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, verify the suite passes, review the diff, and commit the result on your feature branch. ## Quick Start Implement the work described in the current spec or tickets using TDD, then review and commit it to this 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 AI?▼

Provide the spec or tickets and invoke the implement workflow. The AI builds the described work using TDD at pre-agreed seams, runs typechecking and tests along the way, then reviews and commits the result.

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

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

Does the implement skill run the full test suite on every change?▼

No. It runs typechecking and individual test files regularly during development, but the full test suite runs only once at the end to avoid slow feedback loops while coding.

What happens after the implementation is finished?▼

After the work is complete, the workflow invokes a code review pass over the changes and then commits the work to the current branch, so the result is reviewed and versioned.

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

Avoid it for exploratory spikes or throwaway prototypes where no spec or tickets exist and TDD overhead adds no value. It is designed for agreed, well-defined work that should be tested, reviewed, and committed.

Related Skills

Explore More Software Engineering Skills→
skytiger6724skytiger6724
2

planning-and-task-breakdown

Break integration specs into ordered, verifiable tasks with dependencies and acceptance criteria.

Community
Intermediate
vercelvercel
142.0k

backport-pr

Backport merged Next.js pull requests from canary to older release branches.

Official
Intermediate
stencilastencila
902

software-code-refactoring

Refactor production code while preserving all existing test behavior.

Official
Advanced
KbediakoKbediako
3

standalone-review

Conducts on-demand reviews of tasks and specifications without running pipelines.

Community
Basic