agentsclimarketplace
Sign in

Create github issue feature from specification

Skill mouadja02/skills/skills/product-management/create-github-issue-feature-from-specification

Create GitHub Issue for feature request from specification file using feature_request.yml template.From its SKILL.md

Install
npx -y skills add mouadja02/skills --skill create-github-issue-feature-from-specification

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 9 stars9 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

0.9 KB, 143 tokens by cl100k_base, as published. Nobody here has run it

Create GitHub Issue from Specification

Create GitHub Issue for the specification at ${file}.

Process

  1. Analyze specification file to extract requirements
  2. Check existing issues using search_issues
  3. Create new issue using create_issue or update existing with update_issue
  4. Use feature_request.yml template (fallback to default)

Requirements

  • Single issue for the complete specification
  • Clear title identifying the specification
  • Include only changes required by the specification
  • Verify against existing issues before creation

Issue Content

  • Title: Feature name from specification
  • Description: Problem statement, proposed solution, and context
  • Labels: feature, enhancement (as appropriate)

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most plan spec skills give in 143 tokens

Counted across 1,360 of the 2,617 authors here whose files we hold, read 2026-09-06

  • Ask one question at a timein 73 of 1360
  • Write the spec using the templatein 22 of 1360
  • Ask clarifying questions if neededin 19 of 1360, across 18 files
  • Wait for user confirmation before proceedingin 19 of 1360
  • Save plans to the plans directoryin 17 of 1360, across 13 files
  • Check for product marketing context firstin 16 of 1360, across 5 files
  • Read the plan file completelyin 16 of 1360
  • Order tasks by dependencyin 16 of 1360
  • Gather context from the conversationin 15 of 1360, across 9 files
  • Explore the codebase instead of askingin 15 of 1360, across 13 files
  • Wait for explicit user approvalin 14 of 1360, across 13 files
  • Quiz the user on the breakdownin 13 of 1360, across 7 files

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.