sub-issue-maker

Break down high-level product goals into concrete subtasks with ownership, estimates, dependencies, and acceptance criteria.

1|2|Updated Jul 5, 2024
One-click install
npx skills add https://github.com/uuta/dotfiles --skill sub-issue-maker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sub-issue-maker
Source: https://github.com/uuta/dotfiles/tree/main/skills/sub-issue-maker
Command: npx skills add https://github.com/uuta/dotfiles --skill sub-issue-maker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams break down high-level goals into concrete, actionable subtasks, reducing scope gaps and speeding up delivery.

Core Features & Use Cases

  • Task granularity: Break complex goals into smaller, testable tasks.
  • Domain-agnostic: Applies to frontend, backend, or infra work.
  • Use Case: Given a new feature request, slice it into subtasks for design, API, and UI.

Quick Start

Provide a high-level feature idea, such as 'user profiles', and request a detailed subtasks breakdown.

Frequently Asked Questions about sub-issue-maker

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

FAQPage Schema
How do I break down high-level product goals into concrete subtasks?

To break down high-level product goals into concrete subtasks, provide a feature idea to receive a structured task list. The output includes specific task granularity with defined ownership, time estimates, dependencies, and acceptance criteria.

What is the best way to slice a complex feature request for sprint planning?

Slicing a complex feature request for sprint planning involves dividing it into smaller, testable tasks across frontend, backend, or infrastructure domains. This breakdown reduces scope gaps and speeds up delivery by ensuring all components have clear acceptance criteria.

Does subtask generation work for both frontend and backend infrastructure work?

Subtask generation works for frontend, backend, and infrastructure work. The process is domain-agnostic, meaning you can input any high-level technical goal and receive a detailed subtask breakdown tailored to that specific technical domain.

How do I estimate dependencies and ownership when scoping a new feature?

To estimate dependencies and ownership when scoping a new feature, process the high-level request through task slicing. The resulting output explicitly assigns ownership and maps out task dependencies alongside time estimates for each individual component.

When do I need to slice big tasks into smaller testable tasks?

You need to slice big tasks into smaller testable tasks when preparing for sprint scoping or evaluating release readiness. Breaking down complex goals ensures clear task granularity, which minimizes scope gaps and accelerates overall delivery.

Can I use this for release readiness evaluation across different technical domains?

You can use this for release readiness evaluation across frontend, backend, and infrastructure domains. By breaking down the remaining high-level goals into granular subtasks, you can verify that all necessary components have defined estimates and acceptance criteria.