agentleFS
Sign inStart free
davidsolheimdavidsolheim/skills/issues/SKILL.md

issues

Skill1 starsChanged 38 days agoNo licenceView on GitHub

Research a multi-item product/code dump in the current repo and file many execution-ready `.wcp/issues/` files in one pass so cheaper models can implement each leaf from the ticket alone. Decompose into atomic solve-ready leaves that may be independent or blocked on another file. Reuses /issue execution-ready quality bar (code map, contracts, step plan, file-by-file, AC, drift check) with shared investigation + batch duplicate scan. Use when the user runs /issues, says "file these issues", "ticket this list", or pastes a multi-bullet brain dump / residual backlog. Does not implement code. Prefer /issue for a single one-shot ticket. Prefer /project-review when the agent must invent findings without a user laundry list.

21 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use prd, architecture and 2 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.
  • GitHubSkill

    prd

    Generate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis.

    Also in 6 projects that use this

  • AnthropicSkill

    architecture

    Create or evaluate an architecture decision record (ADR). Use when choosing between technologies (e.g., Kafka vs SQS), documenting a design decision with trade-offs and consequences, reviewing a system design proposal, or designing a new component from requirements and constraints.

    Also in 3 projects that use this

  • SentrySkill

    review

    Fixture review skill.

    Also in 6 projects that use this

  • SentrySkill

    commit

    Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.

    Also in 5 projects that use this

The file

Show its rules and text

We split this skill into the rules it gives an agent

25 rules. 0 are common, 15 are distinctive, and 10 are very specific to this project.

  • 0

    Common

    Most of the 20 edited versions we read keep these.

  • 15

    Distinctive

    This author's own choices. Worth a look.

  • 10

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 20 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.

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