Verified:GitHub

implement

Implements work items from specs or tickets using test-driven development.

Updated Sep 19, 2026

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

One-click install

npx skills add https://github.com/Ab0umar/selrs.cc.BU --skill implement-ab0umar

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/Ab0umar/selrs.cc.BU/tree/main/.agents/skills/implement
Command: npx skills add https://github.com/Ab0umar/selrs.cc.BU --skill implement-ab0umar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a written spec or ticket into working, verified code requires discipline: writing tests first, running typechecks, and reviewing the result. This Skill enforces that structured implementation workflow so work is completed consistently and committed cleanly. ## Core Features & Use Cases - Spec-Driven Implementation: Builds the work described in a spec or set of tickets rather than ad-hoc changes. - TDD Workflow: Applies test-driven development at pre-agreed seams, with regular typechecking and single test file runs during development. - Built-In Review and Commit: Runs a full test suite at the end, invokes /code-review on the finished work, and commits to the current branch. - Use Case: You have a ticket describing a new API endpoint. Invoke this Skill to implement it with tests, verify the full suite passes, review the diff, and commit the result. ## Quick Start Ask the agent to implement the work described in your spec or tickets using the implement 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 ticket with test-driven development?▼

Invoke this Skill with the spec or ticket content. It applies TDD at pre-agreed seams, runs typechecking and single test files regularly during development, and runs the full test suite once at the end before committing.

What happens after the implementation is finished?▼

After the full test suite passes, the Skill invokes /code-review to review the completed work, then commits the changes to the current branch.

Can this Skill be invoked automatically by the AI?▼

No. The Skill sets disable-model-invocation to true and its policy disallows implicit invocation, so it only runs when the user explicitly requests it.

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

Avoid it for trivial one-line fixes or exploratory prototyping where writing tests first adds overhead without value. It is designed for defined work items with clear acceptance criteria.