agentleFS
Sign inStart free
taixuanntaixuann/development-space/.agents/skills/create-github-issues-feature-from-implementation-plan/SKILL.md

create-github-issues-feature-from-implementation-plan

Skill1 starsChanged 12 days agoMITView on GitHub

Create GitHub Issues from implementation plan phases using feature_request.yml or chore_request.yml templates.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Create GitHub Issues for the implementation plan at ${file}.

    line 8
  2. Very specific:

    Check existing issues using search_issues

    line 13
  3. Very specific:

    Create new issue per phase using create_issue or update existing with update_issue

    line 14
  4. Very specific:

    Use feature_request.yml or chore_request.yml templates (fallback to default)

    line 15
  5. Distinctive:

    Verify against existing issues before creation

    line 22

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Create GitHub Issue from Implementation Plan

Create GitHub Issues for the implementation plan at ${file}.

Process

  1. Analyze plan file to identify phases
  2. Check existing issues using search_issues
  3. Create new issue per phase using create_issue or update existing with update_issue
  4. Use feature_request.yml or chore_request.yml templates (fallback to default)

Requirements

  • One issue per implementation phase
  • Clear, structured titles and descriptions
  • Include only changes required by the plan
  • Verify against existing issues before creation

Issue Content

  • Title: Phase name from implementation plan
  • Description: Phase details, requirements, and context
  • Labels: Appropriate for issue type (feature/chore)

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