issue-pool

Manage an issue pool lifecycle by converting vague ideas into actionable tasks in a Markdown file.

752|107|Updated Jan 19, 2026
One-click install
npx skills add https://github.com/yunshu0909/yunshu_skillshub --skill issue-pool
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-pool
Source: https://github.com/yunshu0909/yunshu_skillshub/tree/main/issue-pool
Command: npx skills add https://github.com/yunshu0909/yunshu_skillshub --skill issue-pool

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires markdown, and includes references (resource) components.

What problem does it solve?

Raw ideas and feedback arrive vague and unstructured, making it hard to know what can actually be built. This Skill turns scattered thoughts into a maintained issue pool where every entry is either clarified into a startable task with acceptance criteria, merged with duplicates, or parked with its blocking question recorded.

Core Features & Use Cases

  • Five lifecycle actions: record (capture verbatim with duplicate checks), merge (consolidate related issues), decompose (discuss and uncover the real need behind a proposed solution), convert (produce a simple task or a rolling multi-version plan), and pending (park unclear items instead of fabricating plans).
  • Single-file pool: all issues live in one root-level ISSUES.md with status emoji markers, no kanban boards or new tooling.
  • Framework plan writing: complex issues that cannot ship in one version get a staged plan in docs/plan/ following a seven-step reference workflow, with an included md2html.py tool to render plans as styled HTML.
  • Use Case: A user says "record an issue: the page is too bright at night." The Skill logs it verbatim, flags a similar existing entry, then later helps decompose it into a task with 3-5 acceptance points and a target version.

Quick Start

Ask the agent to record a new issue or review the current issue pool, for example by saying "记个 issue:用户晚上使用时觉得页面太亮" or "过一遍池子".

Frequently Asked Questions about issue-pool

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

FAQPage Schema
How do I turn vague feature ideas into actionable development tasks?

Record each idea verbatim into the issue pool, then use the decompose action to discuss it in at most two rounds of questions. Items deliverable in one version become simple tasks with 3-5 acceptance points; larger ones become rolling framework plans.

What is an issue pool and how is it different from a kanban board?

An issue pool is a single Markdown file (ISSUES.md) at the repository root where each entry carries a status emoji and nested task details. It deliberately avoids kanban boards, databases, or new formats to keep management lightweight.

How do I convert a Markdown plan document to HTML?

Run the bundled md2html.py script with the plan file path, for example python3 tools/md2html.py docs/plan/v1.0-plan.md. It requires the Python markdown package and applies the bundled style.css to produce a standalone styled HTML file.

When should an issue become a plan instead of a simple task?

The deciding criterion is whether the work can be delivered within one version. If yes, it becomes a simple task with acceptance points; if not, it becomes a rolling plan that only details the next one to three versions and leaves later stages intentionally vague.

What are the limitations of this issue management approach?

It does not write PRDs, test cases, code, or design artifacts, and it never sets priorities or creates branches and tags. Those activities belong to downstream skills such as prd-test-writer, design-exploration, and git-push.