agentleFS
Sign inStart free
ishandutta2007ishandutta2007/Awesome-Claude-Skills/skills/to-issues/skill.md

to-issues

Skill16 starsChanged 6 months agoMITView on GitHub

Output: "1. [AFK] Basic Profile View (UI/API/Test). Blocked by: None. 2. [AFK] Profile Edit Schema (DB/API). Blocked by: #1. 3. [HITL] Avatar Upload Strategy. Blocked by: None."

130 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use decision-mapping, modern-go and 7 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • FabienDehopreSkill

    decision-mapping

    Turn a loose idea into a sequenced map of investigation tickets, then drive them to resolution one at a time.

    Also in 7 projects that use this

  • jidechaoSkill

    modern-go

    Modernize Go code by applying version-appropriate idioms and APIs (gofix-style transformations). Scans go.mod for the Go version, then transforms Go source files to use modern patterns—from Go 1.0 through 1.26+. Use when the user says "现代化","现代Go语言", "地道的", "idiomatic", "modernize", "modern-go", "update Go code", "gofix", or wants to upgrade Go idioms.

    Also in 3 projects that use this

  • jidechaoSkill

    loop-it

    Automated issue loop with checkpoint/resume: fetch open GitHub issues → dependency-aware topological sort → implement each issue end-to-end → review with /review-it → document with /note-it → ship with /ship-it → repeat. Persists state to .loop-state.json for crash recovery. Triggers on: loop-it, loop issues, auto implement, 批量实现, 循环实现, 实现所有issue, 恢复循环, resume loop.

    Also in 3 projects that use this

  • simo97Skill

    request-refactor-plan

    Use this skill when user wants to create a refactor plan.

    Also in 18 projects that use this

  • simo97Skill

    edit-article

    The user will invoke this skill to help them edit an article.

    Also in 18 projects that use this

  • kennethkeimSkill

    ubiquitous-language

    Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to UBIQUITOUS_LANGUAGE.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions "domain model" or "DDD".

    Also in 17 projects that use this

  • +2 more from jidechao
  • +1 more from simo97

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 123 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Vertical Slices: Every issue must deliver a complete, demoable path (UI -> API -> DB).

    line 10
  2. Distinctive:

    No Stale Paths: Avoid hardcoding file paths in issue descriptions.

    line 13
  3. Distinctive:

    Gather: Read the full plan or reference existing issues/PRDs.

    line 16
  4. Distinctive:

    Draft: Create a list of tracer-bullet issues with titles, types (HITL/AFK), and blockers.

    line 18

“Common” is measured: kept by at least 6 in 10 of the 123 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
skill.md

Skill: Plan to Issues (To Issues)

Role

You are a Technical Project Manager specializing in iterative delivery and vertical slicing.

Objective

Break a large plan, spec, or PRD into small, independently implementable "tracer-bullet" issues that cut through all integration layers.

Constraints

  • Vertical Slices: Every issue must deliver a complete, demoable path (UI -> API -> DB). No horizontal layers.
  • HITL vs AFK: Clearly distinguish between issues needing human judgment (HITL) and those an agent can handle alone (AFK).
  • Dependency Order: Identify what blocks what to ensure a logical build order.
  • No Stale Paths: Avoid hardcoding file paths in issue descriptions.

Process

  1. Gather: Read the full plan or reference existing issues/PRDs.
  2. Explore: Understand the code's current state to ensure the breakdown is realistic.
  3. Draft: Create a list of tracer-bullet issues with titles, types (HITL/AFK), and blockers.
  4. Review: Present to the user and iterate on granularity and dependencies.
  5. Publish: Once approved, create the issues in the tracker, referencing blockers by ID.

Output Format

  • Breakdown: Numbered list of proposed issues.
  • Issue Details: Title, Type, Blocked By, and User Stories covered.
  • Issue Template: Detailed description and acceptance criteria for the tracker.

Examples

Example 1: New Feature Breakdown

Input: "Break down the 'User Profile' feature from the PRD into issues."

Output: "1. [AFK] Basic Profile View (UI/API/Test). Blocked by: None. 2. [AFK] Profile Edit Schema (DB/API). Blocked by: #1. 3. [HITL] Avatar Upload Strategy. Blocked by: None."

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free