implement-spec

Implements specs and tickets as committed Next/React/TypeScript code via test-driven vertical slices.

1|Updated Jul 13, 2026
One-click install
npx skills add https://github.com/dineshrevunuru/SuperSkills --skill implement-spec-dineshrevunuru
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement-spec
Source: https://github.com/dineshrevunuru/SuperSkills/tree/main/implement-spec
Command: npx skills add https://github.com/dineshrevunuru/SuperSkills --skill implement-spec-dineshrevunuru

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a spec or ticket into shipped code often fails in predictable ways: tests retrofitted to match code already written, features committed because they "work" but ship inaccessible controls, and ad-hoc debugging that derails the build. This Skill sequences the implementation loop — agreeing test seams up front, building in vertical red-green slices, and enforcing a review gate before commit — so shipped Next/React/TypeScript features meet their acceptance criteria. ## Core Features & Use Cases - Seam-first planning: Names the public test seams (exported functions, hook returns, route handlers) and confirms them before any code is written, preventing tautological retrofitted tests. - Vertical-slice build loop: Drives one failing behavior test per slice via test-shipped-code, with typecheck and test cadence after each slice and a full suite run at the end. - Pre-commit review gate: Runs review-shipped-code as an AND-gate on the diff, blocking commit if either the Standards or Spec axis fails, then commits to the feature branch under git guardrails. - Use Case: Given a workpack ticket to add a "Book again" action to a salon booking confirmation screen, agree the buildRebookPayload seam, write the failing test first, implement to green, catch an inaccessible motion.div button at the review gate, fix it, and commit. ## Quick Start Implement the next ready ticket from my workpack spec as committed code, agreeing the test seams first and running the review gate before committing.

Frequently Asked Questions about implement-spec

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement a spec or ticket as committed code with TDD?

Agree the public test seams up front, then build in vertical slices: one failing behavior test per seam, just enough code to pass it, and typecheck plus test runs after each slice. Finish with a full suite run and a review gate before committing to the feature branch.

What is a test seam and why agree it before writing code?

A seam is a public boundary where behavior is tested, such as an exported function, hook return, or route handler. Agreeing seams before coding prevents retrofitting tests that merely echo the implementation, which is a tautological test that proves nothing.

Does this workflow require Jira or Linear tickets?

No. It is solo-first: tickets can come from a workpack BUILD-SPEC, prd.md, tasks.json acceptance criteria, or a plain markdown checklist. It only mode-switches up to Jira, Linear, or GitHub Issues when the project actually has a tracker.

Should I use this for building a coded prototype?

No. Prototypes are explicitly out of scope and belong to a separate prototype-building skill with no tests and no review gate. This loop is for shipped Next/React/TypeScript surfaces where accessibility and standards are enforced before commit.

What happens when a bug appears mid-build?

Stop building and hand the bug to a dedicated diagnose-bugs loop that reproduces, minimizes, fixes, and adds a regression test. Resume the build only after it flips green-red-green, rather than debugging ad hoc inside the build.

When is a feature considered done under this workflow?

Done requires all five criteria: every acceptance criterion met, typecheck clean, full test suite green, the review gate passed, and the work committed to a feature branch. Anything short of all five is not complete.