Agent skill

Zoonk Issue Planning

by zoonk in zoonk/zoonk

Break work into GitHub issues, epics, or dependencies when the user explicitly requests an issue breakdown.

MITAuto-check passedProduct & Project Management

Install Zoonk Issue Planning

skills CLI
$ npx skills add zoonk/zoonk --skill zoonk-issue-planning -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install zoonk/zoonk zoonk-issue-planning --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/zoonk/zoonk.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/zoonk-issue-planning .claude/skills/zoonk-issue-planning && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
zoonk-issue-planning
GitHub stars
157
Token cost
~707 tokens
SKILL.md length
376 words
Files
1
Skills in repo
11
Repo updated
First seen
Licence
MIT

At a glance

Break work into GitHub issues, epics, or dependencies when the user explicitly requests an issue breakdown.

  • Explicitly requests an issue breakdown
  • SKILL.md covers Boundaries and size, Dependencies and Deliverable and authorization
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Tasks that involve User stories

What it does

Zoonk Issue Planning is an agent skill from zoonk/zoonk. Break work into GitHub issues, epics, or dependencies when the user explicitly requests an issue breakdown.

Its SKILL.md is about 710 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Product & Project Management, covering User stories. It works with GitHub. The repository describes itself as: Turn any topic into clear, structured lessons. The licence is MIT.

When your agent uses it

  • Explicitly requests an issue breakdown
  • Tasks that involve User stories

Example prompts

  • “/zoonk-issue-planning”

What it can do on your machine

Read from SKILL.md and the folder at commit d6d96be. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Zoonk Issue Planning loads about 707 tokens when it runs. Until then it costs about 32 tokens; SKILL.md has 376 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~32
When it runs · the whole SKILL.md, loaded when a task matches
~707

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from zoonk/zoonk at commit d6d96be, republished under its MIT licence (© zoonk). 376 words, ~707 tokens.

Download SKILL.mdSave it as .claude/skills/zoonk-issue-planning/SKILL.md (or your agent's skills folder).
name
zoonk-issue-planning
description
Break work into GitHub issues, epics, or dependencies when the user explicitly requests an issue breakdown.
license
MIT
metadata.author
zoonk
metadata.version
2.0.0

Issue planning

Produce a coherent breakdown of the requested work into independently reviewable outcomes. This skill applies to explicit issue planning; ordinary feature implementation or recording a single problem does not require an epic.

Boundaries and size

  • Group changes that must ship together, including their types, migrations, and relevant tests. Keep one source of truth for shared contracts and respect the repository's core/app boundaries.
  • Prefer small issues that can be implemented and reviewed coherently. Treat estimated line count as a sizing signal, not a hard limit; do not split one capability solely to fit a quota.
  • Split at real feature, resource, or integration boundaries. Related endpoints can share an issue when they form one capability; do not prescribe one issue per endpoint.
  • Keep testing and verification with the implementation they establish. Do not create separate generic testing or verification issues. A task specifically about a testing defect can stand on its own.
  • Use sub-epics only when a substantial domain benefits from its own tracking. Avoid empty hierarchy around a few tasks.

Dependencies

Add a dependency when one deliverable is required by another, integration cannot proceed without it, or simultaneous changes would conflict. Leave independent work unblocked. Inspect actual contracts rather than automatically making all frontend work wait for all backend work.

Use local identifiers or spec filenames in drafts, such as api-search or 02-course-search.md. Do not use #123 for local numbering; GitHub assigns issue numbers later. Preserve a local-identifier-to-GitHub-number mapping if the plan is published.

Show full SKILL.md (131 more words)Show less

Deliverable and authorization

For each planned issue, give its intended outcome and real dependencies; include verification in a requested implementation plan in proportion to the change. Use a compact list or table, adding a dependency diagram only when it clarifies the work.

For published issue bodies, follow zoonk-github-issues: preserve the problem and desired outcome rather than copying internal estimates, temporary paths, or a generic implementation checklist. Add technical detail when the user requested a specification; keep the parent epic focused on the overall problem.

A request to plan ends with a reviewable plan. If the user also asked to create the issues, proceed through that authorized publication using the GitHub issue skill without requiring a second planning approval. Do not assign owners, add time estimates, or change product scope unless requested.

© zoonk, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/zoonk-issue-planning of zoonk/zoonk.

Open the folder on GitHubat commit d6d96be

Compare with similar skills

Zoonk Issue Planning next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Zoonk Issue Planning compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Zoonk Issue Planning this skillzoonk/zoonk157—~707Automated safety check: PassMIT
Create Issuetradingstrategy-ai/frontend150—~607Automated safety check: PassNone
Specgetsentry/sentry-react-native1.8k—~1.1kAutomated safety check: PassMIT
Abo Issue Watcherjeeftor/audiobook-organizer190—~417Automated safety check: PassMIT
SpecifyRafaelGB/Obsidian-ZettelFlow174—~759Automated safety check: PassMIT
Execute Issuelbedner/aegis-stack143—~1.1kAutomated safety check: PassMIT

Similar skills

  • Create Issue

    tradingstrategy-ai/frontend

    Creates a new GitHub issue with structured user story format, acceptance criteria, and project integration.

    150 GitHub stars~607 tokensUpdated 2 days ago
    Product & Project ManagementAuto-check passed
  • Spec

    getsentry/sentry-react-native

    Official

    Produce a verified spec — problem, desired outcome, and acceptance criteria — before building.

    1.8k GitHub stars~1.1k tokensUpdated yesterday
    Product & Project ManagementAuto-check passed
  • Abo Issue Watcher

    jeeftor/audiobook-organizer

    Inspect Audiobook Organizer GitHub issues, comments, acceptance criteria, linked PRs, and next steps.

    190 GitHub stars~417 tokensUpdated 29 days ago
    Product & Project ManagementAuto-check passed
  • Specify

    RafaelGB/Obsidian-ZettelFlow

    Stage 1 of the SDD pipeline — write a ZettelFlow spec into a GitHub issue body (problem, value, functional requirements, testable acceptance criteria, capability disclosure, out-of-scope).

    174 GitHub stars~759 tokensUpdated yesterday
    Product & Project ManagementAuto-check passed
  • Execute Issue

    lbedner/aegis-stack

    A skill your agent uses when handed a GitHub issue (number or URL) to execute end to end.

    143 GitHub stars~1.1k tokensUpdated yesterday
    Product & Project ManagementAuto-check passed
  • Create Issue Gate

    sickn33/agentic-awesome-skills

    A skill your agent uses when starting a new implementation task and an issue must be created with strict acceptance criteria gating before execution.

    47k GitHub starsUsed in 2 repos~696 tokens
    Product & Project ManagementAuto-check passed

More from zoonk/zoonk

All 11 skills in this repo
  • Workflow

    zoonk/zoonk

    Creates durable, resumable workflows using Vercel's Workflow DevKit.

    157 GitHub stars~3.1k tokensUpdated yesterday
    Auto-check passed
  • A skill your agent uses when designing, reviewing, or implementing Android UI or features for phones, tablets, foldables, ChromeOS, desktop windowing, Wear OS, Android TV, Android for Cars, Android…

    157 GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed
  • A skill your agent uses when designing, reviewing, or implementing any Apple-platform UI or feature for iOS, iPadOS, macOS, visionOS, tvOS, watchOS, SwiftUI, UIKit, AppKit, WatchKit, app icons, Dark…

    157 GitHub stars~942 tokensUpdated yesterday
    Auto-check passed
  • Create or update problem-focused Zoonk GitHub issues and their requested metadata or relationships.

    157 GitHub stars~632 tokensUpdated yesterday
    Auto-check passed
  • Zoonk Commit

    zoonk/zoonk

    Write Zoonk commit messages and PR titles or descriptions when preparing a commit or pull request.

    157 GitHub stars~578 tokensUpdated yesterday
    Auto-check passed
  • Create or refactor reusable Zoonk React UI primitives using flat compound components.

    157 GitHub stars~583 tokensUpdated yesterday
    Auto-check passed

Works with

Questions about Zoonk Issue Planning

What does Zoonk Issue Planning do?

Break work into GitHub issues, epics, or dependencies when the user explicitly requests an issue breakdown. Zoonk Issue Planning is an agent skill from zoonk/zoonk. Break work into GitHub issues, epics, or dependencies when the user explicitly requests an issue breakdown.

When should I use Zoonk Issue Planning?

Zoonk Issue Planning fits situations like: explicitly requests an issue breakdown; tasks that involve User stories.

How do I install Zoonk Issue Planning in Claude Code?

Run `npx skills add zoonk/zoonk --skill zoonk-issue-planning -a claude-code`. Or copy the skill folder (.agents/skills/zoonk-issue-planning in zoonk/zoonk) into .claude/skills/zoonk-issue-planning in your project. Claude Code loads it when a task matches its description.

How do I install Zoonk Issue Planning in Codex?

Run `npx skills add zoonk/zoonk --skill zoonk-issue-planning -a codex`. Or copy the skill folder (.agents/skills/zoonk-issue-planning in zoonk/zoonk) into .agents/skills/zoonk-issue-planning in your project. Codex loads it when a task matches its description.

Can I use Zoonk Issue Planning in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add zoonk/zoonk --skill zoonk-issue-planning -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/zoonk-issue-planning, .gemini/skills/zoonk-issue-planning, .github/skills/zoonk-issue-planning and .opencode/skills/zoonk-issue-planning in your project.

What does Zoonk Issue Planning need to run?

SKILL.md names no scripts, command-line tools or credentials: Zoonk Issue Planning is instructions for the agent only.

Does Zoonk Issue Planning access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Zoonk Issue Planning safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Zoonk Issue Planning use?

Zoonk Issue Planning is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Zoonk Issue Planning use?

About 707 tokens (SKILL.md is roughly 2.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Zoonk Issue Planning?

Skills that share tags, products or a category with Zoonk Issue Planning: Create Issue (tradingstrategy-ai/frontend, 150 stars), Spec (getsentry/sentry-react-native, 1.8k stars), Abo Issue Watcher (jeeftor/audiobook-organizer, 190 stars) and Specify (RafaelGB/Obsidian-ZettelFlow, 174 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Zoonk Issue Planning?

zoonk (a GitHub organization) maintains it in zoonk/zoonk, which has 157 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 8, 2026.

Source: zoonk/zoonk on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.