skills.rest
AlexanderNarbaev
AlexanderNarbaevCOMMUNITY
Explore all skills by this author →
𝕏@alex_foullyGitHub

implement

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

Updated May 31, 2026
Search Tags:#testing#tdd#code review#spec#tickets#implement#typechecking
One-click install
npx skills add https://github.com/AlexanderNarbaev/agi --skill implement-alexandernarbaev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/AlexanderNarbaev/agi/tree/main/.opencode/skills/matt-pocock/implement
Command: npx skills add https://github.com/AlexanderNarbaev/agi --skill implement-alexandernarbaev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a written spec or a set of tickets into working, verified code requires discipline: writing tests first, running typechecks, and reviewing the result. This Skill structures that process so implementation work follows a consistent, test-driven workflow instead of ad-hoc coding. ## Core Features & Use Cases - Spec-Driven Implementation: Builds the work described by the user in a spec or ticket set. - 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 with a code review pass and commits 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 changes, and commit them to your branch. ## 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 feature from a spec or tickets?▼

Provide the spec or ticket set to the implement skill, which builds the work using test-driven development at pre-agreed seams. It runs typechecking and tests during development, then reviews and commits the finished work.

How does test-driven development fit into the implementation workflow?▼

TDD is applied at pre-agreed seams, meaning tests are written first at defined boundaries rather than everywhere. Typechecking and single test files run regularly, with the full test suite executed once at the end.

Does the implement skill commit code automatically?▼

Yes, after the implementation passes review, the skill commits the work to the current branch. It does not create new branches or push to remotes on its own.

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

Avoid it for exploratory spikes or throwaway prototypes where no spec or tickets exist and test coverage is not required. The workflow assumes defined requirements and a codebase with typechecking and tests.

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
RooseveltAdvisorsRooseveltAdvisors
1

DevFlow

Detect the current development stage and enforce CI/CD pipeline adherence.

Community
Advanced
imankhaimankha

lint

Run static analysis on frontend JS/JSX code with ESLint.

Community
Intermediate
notdpnotdp
8

chrome-devtools-mock

Intercept browser API calls to mock frontend data without changing source code.

Community
Intermediate