to-issues
๐ฏSkillfrom mattpocock/skills
|Breaks a plan, spec, or PRD into independently-grabbable GitHub issues using tracer-bullet vertical slices. Each issue is a thin end-to-end path through every integration layer that can be demoed or verified on its own.
Overview
Part of Matt Pocock's "Skills For Real Engineers" collection, /to-issues takes a plan, spec, or PRD and breaks it into independently-grabbable GitHub issues. Each issue is structured as a tracer-bullet vertical slice, meaning it traces a thin end-to-end path through every integration layer so it can be demoed or verified on its own. This skill addresses the common problem where large plans get split into horizontal layers (all backend, then all frontend) that cannot be tested until everything is assembled.
Key Features
- Vertical slice decomposition that produces issues where each one touches every relevant layer (UI, API, database) and can be independently verified
- Tracer-bullet methodology inspired by "The Pragmatic Programmer," ensuring each issue delivers a thin but complete path through the system
- Direct GitHub issue creation that posts structured, independently-assignable issues to your repository
- Works with any input format including PRDs, conversation context, specs, or freeform plans created with
/to-prdor/grill-with-docs
Who is this for?
- Engineering leads and developers who need to decompose large features into manageable, independently-shippable units of work
- Teams using AI agents for planning who want structured issue creation that follows vertical-slice best practices
- Anyone who has experienced the pain of horizontal task splitting where nothing works until the last piece is assembled
Same repository
mattpocock/skills(54 items)
Installation
npx vibeindex add mattpocock/skills --skill to-issuesnpx skills add mattpocock/skills --skill to-issues~/.claude/skills/to-issues/SKILL.mdSKILL.md
More from this repository10
Interviews the user relentlessly about every aspect of a plan or design until reaching shared understanding, resolving each branch of the decision tree one by one. Provides recommended answers for each question and explores the codebase when answers can be found there.
A skill that runs a grilling session to challenge your plan against an existing domain model, sharpen terminology by building a shared language in CONTEXT.md, and document architectural decisions in ADRs before coding begins.
An agent skill from Matt Pocock's engineering toolkit that helps improve your codebase architecture. Part of a composable skill set designed to fix common AI coding agent failure modes through structured, experience-based workflows.
Enforces test-driven development with a strict red-green-refactor loop using vertical slices (one test then one implementation at a time), emphasizing behavior verification through public interfaces rather than implementation-coupled testing.
Initial setup skill for Matt Pocock's engineering skills collection that configures your backlog manager, triage labels, and documentation paths for AI coding agents.
A composable skill for triaging issues and tickets using configurable labels, designed to fix common failure modes in AI coding agents by providing structured backlog management workflows.
A collection of small, composable engineering skills designed for real development workflows, featuring grilling sessions for requirement alignment, issue tracking integration, and task triage with customizable labels.
A skill that turns the current conversation context and codebase understanding into a structured PRD (Product Requirements Document) and submits it as a GitHub issue, with modular architecture and user story generation.
Composable, model-agnostic agent skills for real engineering workflows, featuring /grill-me for requirement alignment, /prototype for rapid iteration, and task management tools designed to fix common failure modes in AI coding agents.
A collection of composable engineering skills by Matt Pocock designed to fix common AI coding agent failure modes: misalignment via grilling sessions, verbosity through shared domain language (CONTEXT.md), code quality with TDD red-green-refactor loops, and codebase entropy with architecture improvement workflows.