skills.rest
jwh3times
jwh3timesCOMMUNITY
Explore all skills by this author →
GitHub

implement

Implements work from specs or tickets using TDD, code review, and PR shipping.

1|Updated Oct 29, 2025
Search Tags:#automation#workflow#tdd#code review#pull request#implementation#tickets
One-click install
npx skills add https://github.com/jwh3times/holland-vip --skill implement-jwh3times
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/jwh3times/holland-vip/tree/main/.agents/skills/implement
Command: npx skills add https://github.com/jwh3times/holland-vip --skill implement-jwh3times

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a spec or set of tickets into reviewed, tested, and committed code involves many manual steps. This Skill orchestrates that entire implementation workflow so nothing is skipped, from test-driven development through the final pull request. ## Core Features & Use Cases - Spec-Driven Implementation: Builds the work described in a spec or tickets, applying 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 Ship Pipeline: Invokes code review, addresses every accepted finding, commits to the current branch, then refreshes docs, writes the changelog entry, regenerates agent artifacts, runs fast gates, and opens or updates the PR. - Use Case: You have a ticket describing a new feature for your Next.js site. Invoke this Skill to implement it with TDD, get the code reviewed, fix the findings, and end with an updated pull request ready for merge. ## Quick Start Ask the agent to implement the work described in your spec or tickets using the implement workflow.

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 using an AI coding agent?▼

Provide the spec or tickets and invoke the implement workflow. The agent builds the work with test-driven development at pre-agreed seams, runs typechecking and tests regularly, then commits the result to the current branch.

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

TDD is applied at pre-agreed seams during implementation. The agent runs typechecking and single test files regularly throughout, then executes the full test suite once at the end before review.

Does the implement workflow include code review before committing?▼

Yes, the workflow invokes a code review step after implementation. Every accepted finding must be addressed and the relevant checks rerun before committing, since the review reports findings but does not apply fixes.

What happens after implementation completes on a branch?▼

The ship step refreshes repo docs, writes the changelog entry required by CI, regenerates agent artifacts, runs the fast gates, and opens or updates the pull request for the branch.

When should I not use a full implement-and-ship workflow?▼

Avoid it for quick experiments, throwaway prototypes, or changes where you do not want a commit and pull request created automatically. The workflow always commits to the current branch and opens or updates a PR.

Related Skills

Explore More Software Engineering Skills→
patternincpatterninc
57

clarity--ticket-writer

Transform vague stakeholder requests into structured engineering work tickets.

Official
Advanced
GenEducationGenEducation

land-and-deploy

Merge a pull request, wait for CI and deployment, and verify production health with canary checks.

Official
Advanced
VibeStackCodesVibeStackCodes

playwright-testing

Automate cross-browser end-to-end testing with Playwright.

Official
Intermediate
aslaiiaslaii

gsd-fast

Execute trivial tasks directly without spawning subagents or creating PLAN.md files.

Community
Basic