skills.rest
Junroot
JunrootCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

plan

Convert design-ready GitHub issues into labeled sub-issues with dependency links.

3|Updated Nov 5, 2023
Search Tags:#automation#workflow#github#plan#sub-issues#project-management#issue-management
One-click install
npx skills add https://github.com/Junroot/Nomat --skill plan-junroot
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/Junroot/Nomat/tree/main/.claude/skills/plan
Command: npx skills add https://github.com/Junroot/Nomat --skill plan-junroot

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates converting completed design-ready GitHub issues into a structured set of sub-issues, enabling teams to plan work by breaking down design goals into actionable tasks with clear ownership.

Core Features & Use Cases

  • Read the selected issue's body and design comments to capture requirements and acceptance criteria.
  • Split design-ready work into independent child issues with task labels.
  • Enforce prerequisite labels (requirement, design, verified) before planning.
  • Document dependencies between sub-issues to guide sequencing.

Quick Start

Select a design-ready issue and run this skill to automatically create structured sub-tasks as separate issues.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I convert design-ready GitHub issues into sub-tasks?▼

To convert design-ready GitHub issues into sub-tasks, an automated workflow reads the parent issue and generates structured child issues. This process splits design goals into actionable tasks with clear ownership and dependency links.

What labels are required to break down an issue into independent tasks?▼

Breaking down an issue into independent tasks requires prerequisite labels: requirement, design, and verified. The automation validates these labels on the GitHub issue before generating task-labeled sub-issues.

Can I automatically create sub-issues with dependencies for project management?▼

Yes, you can automatically create sub-issues with dependencies for project management. The workflow generates child issues, documents dependencies between them to guide sequencing, and records predecessor relationships in the parent issue.

How do I select open issues to generate sub-issues in GitHub?▼

To select open issues to generate sub-issues in GitHub, you can either specify a single issue by its number or filter open issues. The system then reads the selected issue's body and design comments to capture requirements.

What happens if an issue lacks the verified label before planning?▼

If an issue lacks the verified label before planning, the automation enforces prerequisite labels and will halt the process. Issues must carry the requirement, design, and verified labels to proceed with sub-issue generation.

Related Skills

Explore More Product & Management Skills→
JunrootJunroot
3

design

Analyze GitHub issue requirements and draft an implementation design.

Community
Advanced
intent-integrity-chainintent-integrity-chain
47

iikit-09-taskstoissues

Convert tasks from tasks.md into standardized GitHub issues.

Official
Intermediate
codekilncodekiln
3

gh-sub-issue

Link GitHub issues as parent-child sub-issues via the GitHub API.

Community
Intermediate
zoonkzoonk
146

zoonk-github-issues

Plan and manage GitHub issues with types, dependencies, and sub-issues.

Official
Advanced