implement

Implements work from a spec or tickets using test-driven development.

2|2|Updated Dec 23, 2017
One-click install
npx skills add https://github.com/xriu/dotfiles --skill implement-xriu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/xriu/dotfiles/tree/main/home/.skills/mattpocock/implement
Command: npx skills add https://github.com/xriu/dotfiles --skill implement-xriu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a written spec or set of tickets into working, verified code requires discipline: writing tests first, running typechecks, and reviewing the result. This Skill structures that process so implementation work follows a consistent, quality-checked workflow. ## Core Features & Use Cases - Spec-Driven Implementation: Builds the work described in a spec or set of tickets provided by the user. - 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 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 result. ## Quick Start Implement the work described in this ticket 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 ticket with TDD?▼

Provide the spec or ticket and let the Skill implement the work using test-driven development at pre-agreed seams. It runs typechecking and individual test files during development, then the full test suite at the end.

What workflow does this Skill follow for coding tasks?▼

It implements the described work, applies TDD where possible, runs typechecking and single test files regularly, executes the full test suite once at the end, performs a code review, and commits to the current branch.

Does the Skill commit changes automatically?▼

Yes, after implementation and code review are complete, it commits the work to the current branch. It does not create new branches or push to remotes on its own.

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

Avoid it for exploratory prototyping or spikes where requirements are unclear, since the workflow assumes a defined spec or tickets. It is also a poor fit when no test suite or typechecking exists to verify the work.