skills.rest
J0Jng
J0JngCOMMUNITY
Explore all skills by this author →
GitHub

implement

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

7|1|Updated Jul 17, 2026
Search Tags:#testing#tdd#code review#spec#tickets#implement#typechecking
One-click install
npx skills add https://github.com/J0Jng/MathModelingAgents --skill implement-j0jng
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/J0Jng/MathModelingAgents/tree/main/.claude/skills/engineering/implement
Command: npx skills add https://github.com/J0Jng/MathModelingAgents --skill implement-j0jng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a written spec or set of tickets into working, tested code requires discipline: writing tests first, running typechecks, and reviewing the result. This Skill guides the AI through that disciplined implementation workflow so nothing is skipped. ## Core Features & Use Cases - Spec-Driven Implementation: Builds the work described in a spec or ticket set, using test-driven development at pre-agreed seams. - Continuous Verification: Runs typechecking and single test files regularly, then 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 TDD, verify types and tests, review the changes, and commit them on your branch. ## Quick Start Ask the AI 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 with AI?▼

Provide the spec or tickets and invoke the implement skill. It builds the work using test-driven development at pre-agreed seams, runs typechecking and tests along the way, then reviews and commits the result.

How does test-driven development fit into this workflow?▼

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

Does the implement skill run the full test suite?▼

Yes, the full test suite runs once at the end of the work. During implementation, only typechecking and individual test files run regularly to keep iteration fast.

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 concrete spec or tickets. It also assumes an existing test setup and a current branch to commit to.

Related Skills

Explore More Software Engineering Skills→
PacificStudioPacificStudio
264

deep-interview

Clarify ambiguous software requests through a structured Socratic interview.

Official
Advanced
jimmymalhanjimmymalhan
1

no-direct-main

Enforces a no-direct-main policy by routing all changes through pull requests and peer review.

Community
Advanced
kdlbskdlbs
562

verify

Run format, typecheck, tests, and lint across monorepo packages.

Official
Intermediate
ruskicoderruskicoder
3

pair-programming

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

Community
Intermediate