Catalog
mattpocock/implement

mattpocock

implement

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

NewUpdated Oct 8, 2026

Implement the work described by the user in the spec 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.

Call the Skill tool with "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, call the Skill tool with "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

65

Quality

35

Clarity

55

Completeness

25

Summary

This skill directs an AI agent to implement features or fixes based on specifications or issue tickets. It guides the agent to fetch tickets from an issue tracker, apply test-driven development practices where appropriate, run typechecking and test suites, and then invoke code-review and commit the work. The skill is lightweight and relies on downstream skills (tdd, code-review) for actual implementation logic.

Detected Capabilities

issue tracker accessfetch remote specificationsskill invocation (tdd, code-review)git commit operationstypechecking executiontest suite execution

Trigger Keywords

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

implement featurebuild from tickettdd workflowfeature workissue implementation

Use Cases

  • Implement features from GitHub issues or Jira tickets
  • Apply test-driven development to new feature work
  • Run validation checks (typechecking, tests) during implementation
  • Commit completed work after automated code review
  • Guide multi-step implementation workflows with skill composition

Quality Notes

  • Skill is concise but lacks implementation detail — it relies entirely on downstream skills (tdd, code-review) without documenting what those skills do or what contracts they must satisfy
  • No error handling documented — what happens if ticket fetch fails, typechecking fails, or tests fail? Should the agent halt or continue?
  • Scope is unclear — skill says 'call Skill tool with tdd at pre-agreed seams' but does not define what 'pre-agreed' means or how an agent discovers those seams
  • No guidance on handling ambiguous ticket references beyond 'ask' — does not explain how to format the question or what disambiguation criteria to use
  • No documentation of which issue trackers are supported (GitHub Issues, Jira, etc.) or how to pass ticket references
  • Incomplete workflow — commits work but does not describe branch strategy, commit message format, or post-commit actions (push, PR creation, etc.)
  • References 'tdd' and 'code-review' skills but does not validate their existence or provide fallback behavior if they are unavailable
Model: claude-haiku-4-5-20251001Analyzed: Oct 8, 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.2

    Content updated

    ✦ AIAdds instruction to fetch ticket title from issue tracker when user provides a reference.

    2026-10-08

    LATEST
  2. v2.1

    Content updated

    ✦ AIChanges workflow instructions to call the Skill tool with "tdd" and "code-review" instead of using /tdd and /code-review commands.

    2026-10-07

    View This Version
  3. v2.0

    Contract changed: description

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

    triggering2026-09-09

    View This Version
  4. v1.0

    2026-06-18

    View This VersionInitial version

Use mattpocock/implement in your dev environment

Command Palette

Search for a command to run...