implement

Implement work from specs or tickets using test-driven development and code review.

Updated Jul 16, 2026

Search Tags:#testing #tdd #code review #implementation #spec #git commit #typechecking

Ready to run

npx skills add https://github.com/MaksymilianCzadowski/skills --skill implement-maksymilianczadowski

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/MaksymilianCzadowski/skills/tree/main/skills/engineering/implement
Command: npx skills add https://github.com/MaksymilianCzadowski/skills --skill implement-maksymilianczadowski

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 implementation workflow so nothing is skipped. ## Core Features & Use Cases - Spec-Driven Implementation: Executes the work described in a spec or ticket set directly on the current branch. - 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 with a code review pass and commits the completed 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 changes, and commit the result. ## 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 or ticket?▼

Provide the spec or tickets and let the Skill implement the described work on the current branch. It applies test-driven development at pre-agreed seams, runs typechecking and tests, then reviews and commits the result.

How does test-driven development fit into the 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 implementation workflow include code review?▼

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

When should I run the full test suite during implementation?▼

Run typechecking and individual test files regularly while working, but run the full test suite only once at the end. This keeps iteration fast while still verifying the complete codebase before committing.

What are the limitations of spec-driven implementation?▼

The quality of the output depends on the clarity of the spec or tickets; vague requirements lead to ambiguous implementations. TDD is also applied only where possible at pre-agreed seams, so not every code path is necessarily test-first.