Add implement-spec skill (in-progress) with its bucket docs

The skill itself takes a spec plus its tickets and drives them to one
PR, reading the tickets as a task graph so implementer subagents can run
concurrently across the ready frontier.

Documentation duties for the in-progress bucket:

- List it in skills/in-progress/README.md (flat list, name linked to its
  SKILL.md), the one entry every skill in a bucket must have. It stays
  out of the top-level README and .claude-plugin/plugin.json, and gets no
  docs page, as the bucket requires.
- Add a changeset, so the release notes carry it.
- Match the bucket's openai.yaml style in short_description: a short verb
  phrase, no closing period.

Also ignore .claude, which holds settings.local.json and agent worktrees
that should never be committed.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
Matt Pocock
2026-08-21 11:09:36 +01:00
co-authored by Claude Opus 5
parent 0ab1b63a41
commit 84b5ee5afd
5 changed files with 47 additions and 0 deletions
+5
View File
@@ -0,0 +1,5 @@
---
"mattpocock-skills": patch
---
Add the `implement-spec` skill (in-progress bucket, user-invoked). It takes a spec and its tickets and drives them to a single PR: the tickets are read as a task graph with blocking edges, so implementer subagents run in background worktrees across the ready frontier for concurrency, a merger subagent folds each one back into the PR branch, and the flow closes with `/code-review` before the PR is marked ready.