to-issues

Break product plans into independent issue tracker tasks with acceptance criteria.

Updated Aug 26, 2024

Search Tags:#project management #prd #engineering workflow #vertical slices #tracer bullets #issue planning

Ready to run

npx skills add https://github.com/FabienDehopre/my-netatmo-24 --skill to-issues-fabiendehopre

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: to-issues
Source: https://github.com/FabienDehopre/my-netatmo-24/tree/main/.agents/skills/to-issues
Command: npx skills add https://github.com/FabienDehopre/my-netatmo-24 --skill to-issues-fabiendehopre

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps transform broad plans, specifications, or product requirements into clearly scoped issues that engineering teams can independently execute, reducing ambiguity and improving delivery flow.

Core Features & Use Cases

Vertical Slice Planning: Breaks initiatives into tracer-bullet issues that deliver complete, verifiable slices of functionality.
Issue Drafting: Creates structured issue descriptions with acceptance criteria, dependencies, and implementation-ready context.
Use Case: Convert a product roadmap item or PRD into a sequence of well-defined tracker issues that teams can review, prioritize, and implement.

Quick Start

Use the to-issues skill to break this product plan into independent vertical slice issues ready for review.

Frequently Asked Questions about to-issues

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I break down a PRD into actionable engineering issues?▼

To break down a PRD into actionable engineering issues, you decompose broad product plans into independently executable tracker tasks. This process applies vertical slice planning to create structured issues with clear acceptance criteria and dependency ordering.

What is vertical slice planning for issue creation?▼

Vertical slice planning for issue creation is breaking initiatives into tracer-bullet issues that deliver complete, verifiable slices of functionality. It transforms broad specifications into independently executable tasks with implementation-ready context and acceptance criteria.

How do I convert a product roadmap into executable tracker tasks?▼

You convert a product roadmap into executable tracker tasks by applying issue drafting techniques that generate structured descriptions. This involves user story mapping, dependency ordering, and project-specific triage conventions to ensure teams can independently execute the work.

What's the best way to structure issue descriptions for engineering teams?▼

The best way to structure issue descriptions for engineering teams is to include clear acceptance criteria, dependencies, and implementation-ready context. Structured issue creation ensures tasks are independently executable and reduces ambiguity for improved delivery flow.

Do I need specific project triage conventions to plan vertical slice issues?▼

Yes, applying project-specific triage conventions is required when planning vertical slice issues. The decomposition workflow relies on these conventions alongside user story mapping and dependency ordering to sequence well-defined tracker issues for team review and implementation.