Verified:GitHub

implement

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

Updated Jan 19, 2023

Search Tags:#testing #tdd #code review #implementation #spec #tickets #typechecking

One-click install

npx skills add https://github.com/inkfin/dotfiles --skill implement-inkfin

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/inkfin/dotfiles/tree/main/dot_agents/skills/exact_implement
Command: npx skills add https://github.com/inkfin/dotfiles --skill implement-inkfin

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 guides the AI through that disciplined implementation workflow so the delivered work is verified and committed. ## Core Features & Use Cases - Spec-driven implementation: Builds the work described in a spec or ticket set 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. - Review and commit: Invokes a code review pass on the finished work and commits it to the current branch. - Use Case: You hand the AI a feature ticket describing a new API endpoint; it implements the endpoint with tests, typechecks the codebase, reviews the diff, and commits the result. ## Quick Start Ask the AI to implement the work described in your spec or tickets using this skill.

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 with AI?▼

Provide the spec or tickets describing the work, and the skill implements it following a test-driven approach. It runs typechecking and tests during development, reviews the result, and commits to the current branch.

How does test-driven development work in this workflow?▼

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

Does the implementation get reviewed before committing?▼

Yes, after the work is complete the skill invokes a code review pass on the changes. Only after review does it commit the work to the current branch.

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

Avoid it for exploratory prototyping where requirements are unclear, since the workflow expects a defined spec or tickets. It also assumes an existing test suite and typechecking setup in the project.