skills.rest
dulltackle
dulltackleCOMMUNITY
Explore all skills by this author →
GitHub

implement

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

Updated Jun 26, 2026
Search Tags:#testing#tdd#code review#implementation#tickets#git commit#typechecking
One-click install
npx skills add https://github.com/dulltackle/kangkang-skills --skill implement-dulltackle
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/dulltackle/kangkang-skills/tree/main/implement
Command: npx skills add https://github.com/dulltackle/kangkang-skills --skill implement-dulltackle

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a written spec or ticket into working, reviewed, and committed code involves many manual steps: writing tests, running typechecks, reviewing changes, and committing. This Skill orchestrates that entire implementation workflow so nothing gets skipped. ## Core Features & Use Cases - Spec-to-Code Implementation: Builds the work described in a spec or set of tickets following test-driven development at pre-agreed seams. - Continuous Verification: Runs typechecking and single test files regularly, plus the full test suite once at the end. - Delegated Code Review: Spawns a read-only subagent to run an open code review, then validates and fixes its findings before committing. - Use Case: You have a ticket describing a new API endpoint. Invoke this Skill to implement it with TDD, get an automated review pass, fix any findings, and commit the result to the current branch. ## Quick Start Implement the work described in the current spec or tickets using test-driven development and commit the result.

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

Provide the spec or ticket and invoke the implement workflow. It writes tests at pre-agreed seams first, implements the code, runs typechecking and tests regularly, and finishes with the full test suite.

How does automated code review work after implementation?▼

After implementation, a read-only subagent is spawned with the ticket context to run a delegated code review. Its findings are validated, real issues are fixed, and the affected tests are rerun before committing.

When are tests run during the implementation workflow?▼

Typechecking and single test files run regularly throughout implementation. The full test suite runs once at the end, and affected tests are rerun after fixing any code review findings.

Does the implement skill commit changes automatically?▼

Yes, after implementation and review fixes are complete, it commits the work to the current branch using the to-commit step. It does not create branches or push to remotes on its own.

What are the limitations of spec-driven implementation?▼

The quality of output depends on the clarity of the spec or tickets provided. Ambiguous requirements may need clarification first, and the workflow assumes a project with existing typechecking and test infrastructure.

Related Skills

Explore More Software Engineering Skills→
Evolutionary-LeadershipEvolutionary-Leadership

implement

Implements tickets from a spec by working the unblocked frontier with TDD and reporting.

Official
Intermediate
Chorus-AIDLCChorus-AIDLC
1.1k

pr-workflow

Automate pull request workflows with git and the GitHub CLI.

Official
Intermediate
devopstalesdevopstales

springboot-verification

Automate Spring Boot verification with build, static analysis, tests, and security scans.

Community
Advanced
selfagencyselfagency

cavecrew

Route programming tasks to cavecrew subagents for codebase navigation, edits, and reviews.

Community
Intermediate