domains / software-engineering / implement-spec / implement

implement

Skill card

combined

The second copy is a direct derivative of the first (it cites mattpocock/skills as the source), but it materially rewrites the procedure. It replaces the explicit 'tdd' and 'code-review' Skill tool calls with conditional, environment-aware instructions ('/tdd is an upstream command, not a promised available host tool', 'Use /review only when available; otherwise perform the review directly'). It also adds strict safety constraints about committing only to a topic branch and inspecting staged files, which the first copy lacks. Because the second copy introduces real alternative steps and safety constraints that the first does not have, crowning the first would hide a safer, more robust implementation procedure.

Repositories

Other copies

Combined skill

---
name: implement
description: Implement a piece of work based on a spec, PRD, or set of tickets.
---

Implement the work described by the user in the spec, PRD, or tickets.

If the user passes a ticket reference, fetch it from the issue tracker and state its title before starting. If the reference is ambiguous, ask.

Use the project's actual test workflow at pre-agreed seams. If a TDD skill or command is available, use it; otherwise, follow the project's standard test-driven development practices. Preserve the attached plan and existing todos.

Run typechecking regularly, single test files regularly, and the full test suite once at the end.

Review the net diff and actual verification evidence. If a code-review skill or command is available, use it; otherwise, perform the review directly.

Commit only the authorized scope on a topic branch following repository policy. Inspect staged files and preserve unrelated work. Do not commit to a protected default branch or publish merely because implementation was requested.

## Conflicts
- mattpocock/skills: Explicitly calls 'tdd' and 'code-review' Skill tools and commits to the current branch.
- sickn33/agentic-awesome-skills: Uses conditional tool availability checks, emphasizes topic branches, and adds safety constraints for protected branches.