Mp Skills Updates & Release Notes

#1120 2aecca1 Thanks @mattpocock! - Graduate implement-spec into the Engineering bucket, so it ships in the Claude Code plugin, gets a docs page, and is routed by ask-matt as the parallel alternative to per-ticket implement.

implement-spec (user-invoked) implements a whole spec in one run. It reads the tickets as a task graph, runs implementer subagents in their own worktrees across the ready frontier, and lands everything on one integration branch, closing out with code-review. Ahead of graduating:

• The goal is now the integration branch, not a PR. A draft PR opens only when the issue tracker closes work through PRs or you ask for one, and only after the first merge (a branch with no commits ahead of main can't open one). Without a PR, the tickets are resolved the way the tracker closes work.
• It points at the issue tracker like its siblings, telling you to run /setup-matt-pocock-skills when none has been provided, rather than silently defaulting to gh.
• Each implementer confirms its worktree is based on the integration branch, builds its ticket with tdd, and merges the integration tip into its own branch before reporting done, so each merge is a fast-forward. …

#1120 2aecca1 Thanks @mattpocock! - Graduate implement-spec into the Engineering bucket, so it ships in the Claude Code plugin, gets a docs page, and is routed by ask-matt as the parallel alternative to per-ticket implement.

implement-spec (user-invoked) implements a whole spec in one run. It reads the tickets as a task graph, runs implementer subagents in their own worktrees across the ready frontier, and lands everything on one integration branch, closing out with code-review. Ahead of graduating:

• The goal is now the integration branch, not a PR. A draft PR opens only when the issue tracker closes work through PRs or you ask for one, and only after the first merge (a branch with no commits ahead of main can't open one). Without a PR, the tickets are resolved the way the tracker closes work.
• It points at the issue tracker like its siblings, telling you to run /setup-matt-pocock-skills when none has been provided, rather than silently defaulting to gh.
• Each implementer confirms its worktree is based on the integration branch, builds its ticket with tdd, and merges the integration tip into its own branch before reporting done, so each merge is a fast-forward. …

#779 efce423 Thanks @mattpocock! - Make diagnosing-bugs redact secrets.

• Add a Redact section to SKILL.md. The skill has the agent show commands, outputs and captured artifacts; the section makes redaction the first move on each — write <REDACTED>, build loops against env vars so the credential stays in the environment, and quote only the signal-carrying lines of a captured artifact.
• The Phase 1 completion criterion said "paste the invocation and its output". It now says show it redacted, and Phase 1 asks the user for a redacted captured artifact.
• Note in scripts/hitl-loop.template.sh that capture prints its value back to the terminal, so it takes observations while signing in stays a step.

#781 14bfbbd Thanks @mattpocock! - Drop Claude Code's tool and agent-type names from the subagent-dispatch instructions in code-review, codebase-design, and improve-codebase-architecture, so the step is followable on Codex and other harnesses. …

#766 4aaccb5 Thanks @mattpocock! - Make writing-for-agents model-invokable in Codex again.

• Drop policy.allow_implicit_invocation: false from agents/openai.yaml. Codex filtered the skill out of the model-visible skills list, so its description could not trigger it — only an explicit $writing-for-agents mention worked.
• Update the stale interface.display_name and interface.short_description, which still named the old writing-great-skills skill.
• Move the skill from the User-invoked list to the Model-invoked list in README.md and skills/productivity/README.md.

#551 697d4ce Thanks @mattpocock! - Add Codex metadata alongside each skill's Claude Code frontmatter so the set works in both harnesses without generated copies.

• Add an agents/openai.yaml beside every SKILL.md with Codex UI metadata (interface.display_name, interface.short_description).
• Mark every user-invoked skill with policy.allow_implicit_invocation: false, the Codex analog of disable-model-invocation: true, so Codex excludes it from implicit invocation while explicit $skill invocation still works.
• Document the dual-harness invocation model in .agents/invocation.md, CLAUDE.md, and the promoted-bucket READMEs.
• Add AGENTS.md as a symlink to CLAUDE.md so Codex reads the same repo instructions.

#593 0f2bdbd Thanks @mattpocock! - Graduate to-questionnaire out of in-progress/ into the Productivity bucket, so it ships in the plugin. It turns a decision you can't answer alone into a Markdown questionnaire for the one person who can — filled in async, or worked through together in a meeting. …