Catalog
mattpocock/implement

mattpocock

implement

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

NewUpdated Sep 9, 2026

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

Use /tdd where possible, at pre-agreed seams.

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

Once done, use /code-review to review the work.

Commit your work to the current branch.

Files2
2 files · 1.2 KB

Select a file to preview

Overall Score

48/100

Grade

C

Adequate

Grades are signals, not a certification. Always review a skill yourself before use.

Safety

75

Quality

35

Clarity

65

Completeness

28

Summary

This skill instructs an agent to implement work described in specs or tickets using TDD practices. It delegates to other skills (/tdd and /code-review) for specific implementation and review tasks, runs type checking and tests throughout, and commits the work to the current branch when complete.

Detected Capabilities

skill delegation (/tdd, /code-review)test executiontype checkinggit commitbranch-scoped file writes

Trigger Keywords

Phrases that agents use to match this skill to user intent.

implement featurebuild from ticketwrite codetdd workflowcomplete work item

Use Cases

  • Implement feature requirements from a ticket or spec
  • Build new functionality with test-driven development
  • Complete a defined work item with proper verification
  • Implement code changes with built-in quality gates (type checking, testing, review)

Quality Notes

  • Very lightweight skill with minimal prescriptive detail — it reads as a workflow orchestrator rather than a complete implementation guide
  • Assumes user understands TDD and has agreed seams defined; no onboarding or fallback guidance
  • Delegates core logic to /tdd and /code-review skills — content is incomplete without those skills being available
  • No error handling guidance (e.g., what if tests fail? what if type checking reveals errors?)
  • No examples of what 'pre-agreed seams' means or how to recognize them
  • Scope is clear (current branch only) but purpose-driven rather than technically rigorous
  • No edge cases addressed (large specs, ambiguous requirements, merge conflicts)
  • Commit instruction lacks detail — should specify branch, message format, what to commit
Model: claude-haiku-4-5-20251001Analyzed: Sep 9, 2026

Reviews

Add this skill to your library to leave a review.

No reviews yet

Be the first to share your experience.

Version History

  1. v2.0

    Contract changed: description

    ✦ AIUpdates terminology from PRD/issues to spec/tickets, and replaces /review with /code-review command.

    triggering2026-09-09

    LATEST
  2. v1.0

    2026-06-18

    View This VersionInitial version

Use mattpocock/implement in your dev environment

Command Palette

Search for a command to run...