skills.rest
PacificStudio
PacificStudioOFFICIAL
Explore all skills by this author →
GitHub

task-breakdown

Convert clarified specs into OpenASE tickets with dependency edges.

264|27|Updated Mar 19, 2026
Search Tags:#workflow#dependencies#milestones#project-management#systems-design#task-breakdown#ticketing
One-click install
npx skills add https://github.com/PacificStudio/openase --skill task-breakdown-pacificstudio
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: task-breakdown
Source: https://github.com/PacificStudio/openase/tree/main/internal/builtin/skills/task-breakdown
Command: npx skills add https://github.com/PacificStudio/openase --skill task-breakdown-pacificstudio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts a clarified spec into a structured set of OpenASE tickets, parent-child relationships, and dependency edges to maximize safe parallelism and verifiable delivery.

Core Features & Use Cases

  • Generate a minimal yet complete ticket graph consisting of slices, enablers, and milestone gates.
  • Establish explicit dependencies, blocks, and parent-child relationships to guide progress and integration.
  • Produce testable acceptance criteria and proof requirements for each ticket to ensure measurable completion.

Quick Start

Provide a clarified spec and I will generate a minimal, verifiable breakdown into tickets.

Frequently Asked Questions about task-breakdown

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

FAQPage Schema
How do I break down a large project spec into manageable tickets?▼

Breaking down a project spec converts it into a structured set of tickets, parent-child relationships, and dependency edges. This produces a minimal, verifiable breakdown with milestone gates to maximize safe parallelism and guide delivery.

What is the best way to map dependencies for parallel work in project management?▼

Mapping dependencies for parallel work requires establishing explicit blocking edges and milestone gates within a ticket graph. This approach identifies slices, enablers, and hardening phases to enable faster, safer delivery.

Can I generate acceptance criteria and proof requirements for complex requirements?▼

Yes, you can generate testable acceptance criteria and proof requirements for complex requirements. This ensures measurable completion for each ticket within the dependency graph, verifying that milestone gates are met before proceeding.

How do I structure ticket types like slices and enablers for a complex project?▼

Structuring ticket types involves enforcing categories like slice, enabler, and hardening tickets within a dependency graph. This structure ensures explicit milestone gates are met and enables safe parallel work across the project.

When should I use milestone-driven ticketing for systems design?▼

You should use milestone-driven ticketing for systems design when working with large requirements, PRDs, or complex projects. It is needed when explicit milestone gates, blocking edges, and parallel work are required to enable faster delivery.

Related Skills

Explore More Product & Management Skills→
686f6c61686f6c61
105

write-prd

Generate a Product Requirements Document with problem statement, solution, user stories, and acceptance criteria.

Community
Intermediate
richkuorichkuo
45

milestoneplan

Aggregate GitHub milestone issue data into a structured markdown table.

Community
Intermediate
DebuggingInTearsDebuggingInTears

graph-database-expert

Design and optimize graph schemas and traversals for SurrealDB knowledge graphs.

Official
Advanced
ValerianGuivarchValerianGuivarch

ticket-breakdown

Convert technical specifications into structured tickets with separated User Stories and Technical Tasks.

Community
Advanced