domains / families / software-engineering / implement

implement

combined

Implement a piece of work based on a spec or set of tickets. Implement a piece of work based on a PRD or set of issues.

When to use

• Use this skill when you need to implement a piece of work based on a PRD or set of issues. Implement the work described by the user in the PRD or issues. Use the project's actual test workflow at pre-agreed seams; `/tdd` is an upstream com…

When not to use

• Use this skill only when the task clearly matches its upstream source and local project context.
• Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.
• Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.

Skill page

Conflict

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.