zoonk-issue-planning

Name: zoonk-issue-planning
Availability: InStock
Author: Zoonk

Convert implementation plans into GitHub epics with sub-issues and dependencies.

146|12|Updated Jan 30, 2025

Search Tags:#planning #github #dependencies #epics #issues #project-management

Ready to run

npx skills add https://github.com/zoonk/zoonk --skill zoonk-issue-planning

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: zoonk-issue-planning
Source: https://github.com/zoonk/zoonk/tree/main/.agents/skills/zoonk-issue-planning
Command: npx skills add https://github.com/zoonk/zoonk --skill zoonk-issue-planning

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converting high-level implementation plans into a concrete, organized set of GitHub issues so teams can review, assign, and execute with clear scope and traceability.

Core Features & Use Cases

Plan-to-issues mapping: Generate an epic, nested sub-issues, and explicit dependencies from a plan.
Scope management: Define boundaries to prevent scope creep and align work across API, apps, and packages.
Collaborative planning: Provide a reusable structure that teams can reuse for roadmaps and project tracking.

Quick Start

Provide your implementation plan and target milestones; the skill will output a structured breakdown ready for GitHub.

Frequently Asked Questions about zoonk-issue-planning

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

FAQPage Schema

How do I convert an implementation plan into GitHub issues?▼

To convert an implementation plan into GitHub issues, provide your plan and milestones to generate a structured breakdown of epics, nested sub-issues, and explicit dependencies ready for review and assignment.

What is the best way to manage dependencies across multi-domain project issues?▼

Managing dependencies across multi-domain project issues involves translating plans across APIs, apps, and packages into a structured set of GitHub issues, applying explicit dependencies to enable parallel work and clear ownership.

How do I break down a project epic into sub-issues with clear scope?▼

Breaking down a project epic into sub-issues requires translating high-level plans into a structured set of GitHub issues, defining boundaries to prevent scope creep and align work across different domains.

Can I generate a GitHub issue breakdown for parallel work across APIs and apps?▼

Yes, you can generate a GitHub issue breakdown for parallel work by applying your plan across multi-domain areas like APIs, apps, and packages, producing a reusable structure with clear ownership and dependencies.

How do I include tests and verification in my GitHub issue planning?▼

To include tests and verification in GitHub issue planning, translate your implementation plan so that each issue in the breakdown explicitly incorporates its scope, tests, and verification as part of the structured output.