To Issues
Skill AktivBreak a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.
To convert project plans and requirements into a structured set of trackable issues, facilitating agile development workflows and efficient task management.
Funktionen
- Breaks down plans into vertical slices
- Supports issue tracker integration
- Enforces tracer-bullet methodology
- Facilitates HITL/AFK task classification
Anwendungsfälle
- Converting a PRD into implementation tickets
- Breaking down a feature spec into manageable user stories
- Structuring a large project plan into scannable issues
Nicht-Ziele
- Writing actual code for the issues
- Managing project timelines beyond issue creation
- Closing or modifying parent issues
Workflow
- Gather context from conversation or issue reference
- Optionally explore the codebase
- Draft tracer-bullet vertical slices
- Quiz user on granularity, dependencies, and slice types
- Iterate on breakdown until user approval
- Publish approved slices as issues in dependency order
Praktiken
- Agile methodology
- Vertical slicing
- Issue tracking best practices
Voraussetzungen
- Configured issue tracker (GitHub, Linear, or local files)
- Triage label vocabulary for the issue tracker
- An agent capable of interacting with issue trackers
Documentation
- info:Configuration & parameter referenceThe SKILL.md mentions an optional setup step for issue tracker vocabulary but does not detail specific parameters or configuration options for the core functionality.
Versioning
- warning:Release ManagementThe repository has a recent push date but lacks explicit versioning information in the SKILL.md frontmatter, package.json, or GitHub releases, and installation instructions reference `main`.
Installation
/plugin install skills@mattpocock-skillsQualitätspunktzahl
Vertrauenssignale
Ähnliche Erweiterungen
Sprint Plan
100Plan a sprint with capacity estimation, story selection, dependency mapping, and risk identification. Use when preparing for sprint planning, estimating team capacity, selecting stories, or balancing sprint scope against velocity.
Scrum Master Expert
100Advanced Scrum Master skill for data-driven agile team analysis and coaching. Use when the user asks about sprint planning, velocity tracking, retrospectives, standup facilitation, backlog grooming, story points, burndown charts, blocker resolution, or agile team health. Runs Python scripts to analyse sprint JSON exports from Jira or similar tools: velocity_analyzer.py for Monte Carlo sprint forecasting, sprint_health_scorer.py for multi-dimension health scoring, and retrospective_analyzer.py for action-item and theme tracking. Produces confidence-interval forecasts, health grade reports, and improvement-velocity trends for high-performing Scrum teams.
Plan Sprint
99Plan a sprint by refining backlog items, defining a sprint goal, calculating team capacity, selecting items, and decomposing them into tasks. Produces a SPRINT-PLAN.md with goal, selected items, task breakdown, and capacity allocation. Use when starting a new sprint in a Scrum or agile project, re-planning after significant scope change, transitioning from ad-hoc work to structured sprint cadence, or after backlog grooming when items are ready for inclusion.
Github Project Management
99Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning
Shape Up
100Escape the build trap and endless backlogs. Use Basecamp's methodology to ship meaningful work in 6-week cycles with fixed time, variable scope. Use when: **Product planning** to replace endless backlogs; **Feature development** with clear time boundaries; **Team autonomy** when you want self-directed teams; **Scope management** when projects tend to balloon; **Startup development** with limited resources
Design Sprint
100Test big ideas in just 5 days. Apply Google Ventures' proven methodology to go from problem to validated prototype without months of development. Use when: **New product concepts** that need validation before building; **Big feature decisions** with significant investment required; **Stuck teams** needing to break through analysis paralysis; **Startup pivots** when direction is uncertain; **High-risk bets** where failure is expensive