to-issues

Decompose project plans into granular issues with acceptance criteria and dependency mapping.

28|3|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/Minara-AI/cc-connect --skill to-issues-minara-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: to-issues
Source: https://github.com/Minara-AI/cc-connect/tree/main/.claude/skills/to-issues
Command: npx skills add https://github.com/Minara-AI/cc-connect --skill to-issues-minara-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the friction of translating high-level project plans or product requirements into granular, manageable tasks, ensuring that work is broken down into logical, verifiable units.

Core Features & Use Cases

  • Vertical Slicing: Automatically decomposes complex features into tracer-bullet issues that cut across all integration layers.
  • Triage Integration: Standardizes issue creation by applying necessary labels and templates for immediate project tracking.
  • Use Case: When you have a complex PRD or architectural plan, use this skill to generate a list of HITL and AFK tasks that are ready for immediate implementation or review.

Quick Start

Ask the assistant to break the current project plan into vertical slices and publish them as issues to the tracker.

Frequently Asked Questions about to-issues

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

FAQPage Schema
How do I decompose a high-level project plan into actionable issue tracker tickets?

You can decompose high-level project plans by breaking them into vertical tracer-bullet slices that cut across integration layers, generating structured tickets with acceptance criteria and dependency mapping for immediate project tracking.

What is vertical slicing in task decomposition and when do I need it?

Vertical slicing decomposes complex features into tracer-bullet issues that cut across all integration layers. You need it when translating conceptual product requirements into granular, independently-grabbable, and verifiable work units.

Do I need an existing codebase and issue tracker to generate structured tickets?

Yes, generating aligned tickets requires access to the project issue tracker and existing codebase context to ensure domain vocabulary and architectural decisions match the generated tasks.

How do I create tracer-bullet issues with acceptance criteria and dependency mapping?

Provide a complex PRD or architectural plan to the assistant, ask it to break the plan into vertical slices, and it will standardize issue creation by applying necessary labels and templates for tracking.

Can I use this task decomposition approach to generate both HITL and AFK tasks?

Yes, decomposing complex features into vertical slices generates a list of Human-In-The-Loop and Away-From-Keyboard tasks that are ready for immediate implementation or review.

What's the best way to transition from conceptual planning to execution using vertical slices?

The best way is applying vertical tracer-bullet slicing to decompose product requirements into granular issues with acceptance criteria, facilitating a structured transition from conceptual planning to execution.