agentleFS
Sign inStart free
Aquarius-muAquarius-mu/skillManager/skills/gameserver-agent-skills/to-issues/SKILL.md

to-issues

Skill1 starsChanged 52 days agoMITView on GitHub

Break a plan, spec, or PRD into independently-committable issues using vertical slices. Use when converting a plan into trackable work items.

130 other projects use a version of this, 98 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use decision-mapping, modern-go and 9 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
  • +2 more from simo97

The file

We split this skill into the rules it gives an agent

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

  • 2

    Common

    Most of the 123 edited versions we read keep these.

  • 0

    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. Common:

    Prefer many thin slices over few thick ones

    line 29
  2. Common:

    Should any slices be merged or split?

    line 42

“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

To Issues

Break a plan into independently-committable issues using vertical slices (tracer bullets).

Process

1. Gather Context

Work from the plan or PRD already in context. If an issue reference was provided, fetch it from the issue tracker.

2. Explore the Codebase (if needed)

Understand the current code state. Issue titles and descriptions should use the project's domain vocabulary (Manager names, struct names, module names).

3. Draft Vertical Slices

Break the plan into tracer bullet issues. Each issue is a thin vertical slice that cuts through ALL layers end-to-end — sdp definition + Logic + CmdParser + response — NOT a horizontal slice of one layer.

Slices may be HITL (requires human interaction: design decision, deployment approval) or AFK (can be implemented and committed to SVN without human interaction). Prefer AFK over HITL where possible.

Vertical slice rules:

  • Each slice delivers a narrow but COMPLETE path through every layer
  • A completed slice produces a working feature that can be deployed and verified
  • Prefer many thin slices over few thick ones

4. Quiz the User

Present the proposed breakdown as a numbered list. For each slice:

  • Title: short descriptive name
  • Type: HITL / AFK
  • Blocked by: which other slices must complete first
  • Covers: what functionality this slice delivers

Ask the user:

  • Does the granularity feel right?
  • Are the dependency relationships correct?
  • Should any slices be merged or split?
  • Are HITL/AFK assignments correct?

Iterate until the user approves.

5. Publish Issues

For each approved slice, create an issue. Use the template below. Publish in dependency order (blockers first).

Issue Template

## Parent

Reference to the parent plan or PRD (if applicable).

## What to Build

A concise description of this vertical slice. Describe the end-to-end behavior (sdp → logic → response), not layer-by-layer steps.

Avoid specific file paths or code — they go stale. Exception: if a prototype produced a key data structure or state machine snippet, inline it here.

## Acceptance Criteria

- [ ] CmdId enum value added and unique
- [ ] CS/SC structs defined in sdp
- [ ] Logic implemented in Manager
- [ ] CmdParser handler implemented and registered in CommandRegister.h
- [ ] ./build.sh compiles clean
- [ ] Code review passed (no Critical/Important issues)
- [ ] svn commit done

## Blocked By

- [issue reference] OR "None — can start immediately"

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