Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
Other skills

implement

Implement a piece of work based on a spec, tickets, or triaged issues.

svyatov · Static checks on file

Installation

Read the source and dependencies before running a command. Copying does not install or execute anything.

npx skills add svyatov/supermatt --skill implement

About this skill


name: implement description: "Implement a piece of work based on a spec, tickets, or triaged issues." argument-hint: "[spec path, or ticket or issue references]" disable-model-invocation: true license: MIT

Implement the work described by the user in the spec or tickets. Read docs/agents/issue-tracker.md and docs/agents/triage-labels.md first. If either is missing or unreadable, stop and tell the user to run /setup-supermatt-skills in Claude linked installs or Cursor, /supermatt:setup-supermatt-skills from the Claude plugin, $setup-supermatt-skills in Codex, or /skill:setup-supermatt-skills in OMP. Resume only after both required docs exist and have been read. Fetch each ticket you are given with the tracker's Read an issue operation and read it in full. A parent you are asked to pick from is not such a ticket: see below.

When the user names a parent spec and asks for its next ticket, use the configured tracker's List children and Resolve blockers operations. A frontier ticket is an open child of that exact parent, with every blocker confirmed closed, whose state maps to the canonical ready-for-agent role in triage-labels.md: a label on hosted trackers, a Status: value locally. Do not require a numeric blocker count or interpret missing information as zero. For a custom tracker without these named operations, enumerate children from its documented read/list operations and explicit parent links, then read every declared blocker; stop if those operations cannot establish complete membership or blocker state. An incomplete listing stops selection; an unreadable, malformed, or unresolved child's eligibility is blocked and must be reported, not guessed.

Treat ## Parent as an actual Markdown section, not a quoted example or a mention elsewhere. It must identify one unambiguous parent; resolve links to canonical identity and report conflicts with native parentage rather than choosing a convenient match.

Choose the eligible child with the lowest ticket number. A ticket with no code left, because every criterion is already on the default branch or only a human step such as a release remains, is not frontier: name it and what it waits on, then take the next one. With no frontier ticket left, say so, report blocked or unknown candidates, and stop. Name the ticket you picked before you start. When a ticket names a parent, read only the parent's sections the ticket points to or the work needs, with the tracker's Read a section operation where it has one. An assigned migration-map row requires reading the parent's authoritative ## Migration map section before implementation. With no spec or issue, the decisions settled in this conversation are the spec: write them to a file in the OS temporary directory, so the review can check against them.

When two criteria of a ticket cannot both hold (for example, a data shape the ticket names against "no test changes"), ask the user which one wins before you write code, and post the answer on the issue with the Comment on an issue operation. A conflict resolved in silence comes back as a review finding and the same question after the work is done.

When the issue is a pull request, check out its head branch first, and push your commits back to it. If the push is refused (a fork that does not allow maintainer edits), stop and tell the user.

Before you start, record the current commit with git rev-parse HEAD, and on the default branch create a branch named by the repo's convention.

Before changing data contracts, state transitions, shared mutable state, or retryable effects, load codebase-design through the host's skill mechanism. Follow its state-contract guidance for the affected behavior.

Where possible, at pre-agreed seams, load and follow the tdd skill through the host's skill mechanism. Seams that the spec or issue names or the user explicitly confirmed are pre-agreed. Obtain confirmation for any newly reached seam, including refactor and review-fix seams, before writing tests.

Use tdd's affected-seam checks during each cycle. A finished slice is one completed behavior or fixed review finding, and can contain several cycles. Before committing it, complete the repository's full required gate. Reuse checks already green on the same relevant files, dependencies, configuration, and environment; run only the missing or invalidated checks. Chain newly run checks and the commit on their own exit statuses (&&) so a red check stops it. Run checks bare, never through an output filter, and wait for background checks to finish. A handoff or evidence report alone does not require another application build or test run; repository rules, hooks, and CI still apply.

Commit each finished slice to the current branch, so the work lands as small commits instead of one commit that carries the whole ticket. Reference each issue the work implements in each commit message (#<n>, or the file path on a local tracker).

Once every slice is committed, QA the changes since the commit you recorded in a fresh context: this context wrote them, so it shares their blind spots. Spawn one subagent that loads and follows the qa skill through the host's skill mechanism, and give it that commit as the fixed point and the spec path or issue reference as the request, without an implementation summary or suggested verdict. Include a working preview's startup command, URL, worktree, process ownership, and temporary config paths when available, so QA can verify and reuse the setup. Tell it to report back without changing repository files or filing an issue. On each later pass, pass the prior QA report, its tested commit, the fix diff, and the earlier fails with their steps; qa scopes the follow-up. Without subagents, load and follow qa yourself and state the independence gap. Fix each fail test-first by loading and following tdd, commit the fix the same way as the work, and QA again until the verdict has no fail. Name eac

Read the complete source ↗