mirror of
https://github.com/mattpocock/skills.git
synced 2026-07-29 11:02:41 +07:00
Matt PocockandClaude Opus 4.8
90945a1969
Add a user-invoked `to-plan` skill — the sequential, HITL sibling of `to-issues`. Both slice work into tracer-bullet vertical slices, but `to-plan` produces one ordered sequence you drive by hand, one phase per fresh context, rather than parallel independently-grabbable issues. It publishes to the tracker `/setup-matt-pocock-skills` configured, shaped to it: a single sequential `plan.md` for a local tracker, or a parent issue with ordered sub-issues (native sub-issues where supported) for a real one. Registers the skill everywhere CLAUDE.md requires (plugin.json, top-level and bucket READMEs, docs page), updates the `ask-matt` router's main-flow fork to offer both to-issues and to-plan, and adds a changeset. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
6 lines
758 B
Markdown
6 lines
758 B
Markdown
---
|
|
"mattpocock-skills": minor
|
|
---
|
|
|
|
Add a new user-invoked **`to-plan`** skill to the `engineering/` bucket — the sequential, HITL sibling of **`to-issues`**. Both slice work into tracer-bullet vertical slices, but where `to-issues` produces independently-grabbable issues for parallel agents, `to-plan` produces one ordered sequence you drive by hand, one phase per fresh context. It publishes to the tracker `/setup-matt-pocock-skills` configured, shaped to it: a single sequential `plan.md` for a local tracker, or a parent issue with ordered sub-issues (native sub-issues where the platform supports them) for a real one. The `to-*` fork in `ask-matt`'s main flow now offers both, and there's a human-facing docs page at `docs/engineering/to-plan.md`.
|