implement

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

1|Updated Mar 2, 2025
One-click install
npx skills add https://github.com/marjorg/setup --skill implement-marjorg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/marjorg/setup/tree/main/home/.agents/skills/archive/0-matt/implement
Command: npx skills add https://github.com/marjorg/setup --skill implement-marjorg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a written spec or set of tickets into committed, tested code requires coordinating implementation, testing, typechecking, and review. This Skill structures that process so the work is implemented, verified, and committed on the current branch. ## 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. - Review and Commit: Finishes by running a code review of the work and committing it 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 this spec or these tickets, using TDD where possible, then review and commit the changes.

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 describing the work, and the Skill implements it directly. It uses TDD at pre-agreed seams, runs typechecking and tests along the way, then reviews and commits the finished work to the current branch.

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

TDD is applied where possible at pre-agreed seams in the codebase. Single test files run regularly during development, and the full test suite runs once at the end to confirm everything passes.

Does the implementation workflow include code review?

Yes, after the implementation and tests are complete, the work is reviewed using a code review step. Only after that review is the work committed to the current branch.

When is the full test suite run during implementation?

The full test suite runs once at the end of the work, not continuously. During development, typechecking and individual test files run regularly to catch issues early without the cost of full suite runs.

Can I use this workflow without a written spec or tickets?

The Skill is designed around implementing work described by a spec or set of tickets, so a written description of the work is the expected input. Without one, the scope of what to implement would be undefined.