implement

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

Updated Jul 16, 2026

Search Tags:#tdd #code review #commit #spec #tickets #implement #typechecking

One-click install

npx skills add https://github.com/The-Focus-AI/walking-thoughts --skill implement-the-focus-ai

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/The-Focus-AI/walking-thoughts/tree/main/.agents/skills/implement
Command: npx skills add https://github.com/The-Focus-AI/walking-thoughts --skill implement-the-focus-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a written spec or set of tickets into working, verified code requires disciplined execution: writing tests first, running typechecks, and reviewing the result. This Skill structures that implementation workflow so the work is completed, tested, reviewed, and committed consistently. ## Core Features & Use Cases - Spec-driven implementation: Builds the work described by the user in a spec or set of tickets. - Test-driven development: 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 running a code review over the changes 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 types and the test suite, review the diff, and commit the finished work on your branch. ## Quick Start Implement the work described in this spec using TDD, 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 tickets?▼

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

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

TDD is applied where possible at pre-agreed seams during implementation. Typechecking and individual test files run regularly throughout, and the full test suite runs once at the end before review.

Does the implement Skill commit changes automatically?▼

Yes, after the work is implemented and reviewed with the code-review step, the Skill commits the changes to the current branch. It does not create branches or push to remotes.

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

Avoid it when there is no clear spec or ticket defining the work, since the Skill relies on described requirements. Exploratory prototyping or unclear scope should be clarified into tickets first.