implement

Implements a work ticket using acceptance-test-first workflow with locked test commits.

Updated Sep 14, 2026
One-click install
npx skills add https://github.com/Suge8/skills --skill implement-suge8
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/Suge8/skills/tree/main/workflow/implement
Command: npx skills add https://github.com/Suge8/skills --skill implement-suge8

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It enforces a disciplined ticket implementation workflow where acceptance criteria become failing behavior tests before any code is written, preventing untested changes and post-hoc test tampering. ## Core Features & Use Cases - Acceptance-Test-First: Converts each ticket acceptance criterion into a behavior test at the seam defined by the project's test strategy, then verifies it fails for the right reason. - Test Locking: Commits acceptance tests in an isolated commit that becomes read-only, with a diff check at the end to detect any modification of the locked tests. - Exception Handling: Skips the red-green cycle for pure refactors and uses evidence-based verification for non-automatable criteria like visuals or interactions. - Use Case: You claim a ticket changing login behavior. Write the new acceptance tests, watch them fail, lock them in a dedicated commit, implement the full slice freely, then prove the tests pass and the locked tests are untouched. ## Quick Start Use the implement skill to work on ticket 42, writing acceptance tests first and locking them before implementing the change.

Frequently Asked Questions about implement

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

FAQPage Schema
How do I implement a ticket with acceptance tests first?▼

Write each acceptance criterion as a behavior test at the seam defined by your test strategy, run it to confirm it fails because the feature is unimplemented, then commit the tests alone before writing any implementation code.

What is a locked acceptance test commit in TDD workflows?▼

It is a dedicated commit containing only the acceptance tests, created before implementation starts. After implementation, a git diff against that commit must be empty, proving the tests were not altered to make them pass.

When can I skip writing new acceptance tests for a ticket?▼

Skip the red-green cycle when the ticket has no behavior change, such as refactors, renames, or code moves, where existing tests serve as acceptance. Non-automatable criteria like visuals use evidence collection instead.

What happens if the locked acceptance tests were modified?▼

A non-empty diff against the lock commit means the tests were changed after locking, which is treated as tampering. The workflow stops and requires documenting the reason rather than self-approving the change.

Why use path-scoped git commits during implementation?▼

Path-scoped commits use a temporary index so that on a shared checkout they do not accidentally include changes staged by others. If an index.lock conflict occurs, wait and retry the commit.