skills.rest
CYRUS-pinto
CYRUS-pintoCOMMUNITY
Explore all skills by this author →
GitHub

implement

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

Updated Sep 11, 2026
Search Tags:#testing#tdd#code review#implementation#spec#tickets#typechecking
One-click install
npx skills add https://github.com/CYRUS-pinto/pi-bot --skill implement-cyrus-pinto
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/CYRUS-pinto/pi-bot/tree/main/.agents/skills/implement
Command: npx skills add https://github.com/CYRUS-pinto/pi-bot --skill implement-cyrus-pinto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a written spec or set of tickets into working, reviewed code requires discipline across testing, typechecking, and review. This Skill guides the AI through a structured implementation workflow so work is built, verified, and committed consistently. ## 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: Invokes a code review pass on the finished work and commits 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 to your branch. ## Quick Start Implement the work described in the attached spec using test-driven development, 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 or ticket with AI?▼

Provide the spec or tickets describing the work, and the Skill implements it following a test-driven approach. It runs typechecking and tests during development, reviews the result, and commits the changes to the current branch.

How does test-driven development work in this implementation workflow?▼

TDD is applied at pre-agreed seams, meaning tests are written at defined boundaries before the implementation. Single test files run regularly during development, and the full test suite runs once at the end.

Does the implementation workflow include code review?▼

Yes, after the implementation is complete the Skill invokes a code review pass on the work. This happens before the changes are committed to the current branch.

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

Avoid it for exploratory prototyping or spikes where requirements are undefined, since the workflow expects a clear spec or tickets. It also assumes an existing project with typechecking and a test suite configured.

Related Skills

Explore More Software Engineering Skills→
jamestexasjamestexas
2

work-scope

Decompose feature work into reviewable, single-purpose pull requests.

Community
Advanced
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
ruskicoderruskicoder
3

pair-programming

Guides interactive pair programming by proposing code changes and applying edits only on explicit confirmation.

Community
Intermediate