skills.rest
AceCodePt
AceCodePtCOMMUNITY
Explore all skills by this author →
GitHub

implement

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

Updated May 9, 2024
Search Tags:#testing#tdd#code review#spec#tickets#implement#typechecking
One-click install
npx skills add https://github.com/AceCodePt/dotfiles --skill implement-acecodept
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/AceCodePt/dotfiles/tree/main/.config/opencode/flows/implement
Command: npx skills add https://github.com/AceCodePt/dotfiles --skill implement-acecodept

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a written spec or set of tickets into committed, tested code involves many small decisions about testing, verification, and review. This Skill standardizes that process so implementation work follows a consistent, disciplined workflow every time. ## 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. - Built-In Review and Commit: Finishes by running a code review over the changes 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, verify types and the test suite, review the diff, and commit the result on your branch. ## Quick Start Implement the work described in this spec using TDD, run the tests and typechecks, review the changes, and commit them 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 with TDD?▼

Provide the spec or tickets and let the Skill implement the work using test-driven development at pre-agreed seams. It runs typechecking and individual test files during development, then the full test suite at the end.

How to turn tickets into committed code changes?▼

Hand the tickets to this Skill and it implements the described work, verifies it with tests and typechecks, runs a code review, and commits the result to the current branch.

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

No, it runs typechecking and single test files regularly during implementation for fast feedback. The full test suite runs only once at the end before review and commit.

When is code review performed in the implementation workflow?▼

Code review happens after implementation and testing are complete, using the /code-review step. Only after the review does the Skill commit the work to the current branch.

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

Avoid it for exploratory spikes or throwaway prototypes where TDD and full test verification add overhead without value. It fits best when requirements are already captured in a spec or tickets.

Related Skills

Explore More Software Engineering Skills→
skytiger6724skytiger6724
2

planning-and-task-breakdown

Break integration specs into ordered, verifiable tasks with dependencies and acceptance criteria.

Community
Intermediate
Chorus-AIDLCChorus-AIDLC
1.1k

pr-workflow

Automate pull request workflows with git and the GitHub CLI.

Official
Intermediate
Devsoul2026Devsoul2026
150

requesting-code-review

Automate pre-commit verification with static analysis, tests, and lint checks.

Community
Advanced
dug-21dug-21

Pair Programming

Coordinate AI-assisted pair programming roles with automated quality checks.

Community
Advanced