Verified:GitHub

implement

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

1|Updated Jun 2, 2026

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

One-click install

npx skills add https://github.com/SevWren/Daily-Motivation-Brain-Helper --skill implement-sevwren

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/SevWren/Daily-Motivation-Brain-Helper/tree/main/CLAUDE/skills/engineering/implement
Command: npx skills add https://github.com/SevWren/Daily-Motivation-Brain-Helper --skill implement-sevwren

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a written spec or set of tickets into working, reviewed, and committed code requires a disciplined workflow that is easy to skip under time pressure. This Skill enforces a consistent implementation process so work is tested, typechecked, reviewed, and committed every time. ## Core Features & Use Cases - Spec-Driven Implementation: Implements the work described by the user in a spec or set of tickets. - 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 pass 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 first, verify types and the test suite, review the diff, and commit the finished work. ## Quick Start Implement the work described in this spec using TDD, then review and commit it to the current branch.

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 using TDD?▼

Invoke this Skill with the spec or tickets, and it implements the work using test-driven development at pre-agreed seams. It runs typechecking and individual test files regularly, then the full test suite once at the end.

What is the workflow for turning tickets into committed code?▼

The workflow is: implement the ticket's work with TDD, run typechecking and single test files during development, run the full test suite at the end, perform a code review pass, and commit to the current branch.

Does this Skill run the full test suite on every change?▼

No. It runs typechecking and single test files regularly during implementation, and runs the full test suite only once at the end before review and commit.

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

Avoid it for exploratory spikes or throwaway prototypes where there is no spec or ticket and tests would slow down discovery. It is designed for defined work that must be reviewed and committed.