create-github-issues-for-unmet-specification-requirements

create-github-issues-for-unmet-specification-requirements is a skill for Claude Code, Codex from boshi-xixixi/TraeSkill. It costs 31 tokens per session (236 once invoked), scanned A, original, MIT.

A workflow that compares requirements in a specification with the existing code and creates GitHub Issues for requirements that are not implemented. It checks for matching issues before creating duplicates.

In plain words
What is it for?
Use it to audit a specification against a codebase and create one issue for each unmet requirement.
Why use it?
It helps turn missing requirements into trackable work without losing the link between each issue and its source requirement.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

Good fit Use it to audit a specification against a codebase and create one issue for each unmet requirement.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/boshi-xixixi/traeskill/create-github-issues-for-unmet-specification-requirements
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add boshi-xixixi/TraeSkill --skill create-github-issues-for-unmet-specification-requirements
Clone the repo
git clone --depth 1 https://github.com/boshi-xixixi/TraeSkill

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for create-github-issues-for-unmet-specification-requirements

README.md
[![agentmods](https://agentmods.dev/badge/skills/boshi-xixixi/traeskill/create-github-issues-for-unmet-specification-requirements/github.svg)](https://agentmods.dev/skills/boshi-xixixi/traeskill/create-github-issues-for-unmet-specification-requirements)
Your own site
<a href="https://agentmods.dev/skills/boshi-xixixi/traeskill/create-github-issues-for-unmet-specification-requirements"><img src="https://agentmods.dev/badge/skills/boshi-xixixi/traeskill/create-github-issues-for-unmet-specification-requirements/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for create-github-issues-for-unmet-specification-requirements

Your own site · 80×15
<a href="https://agentmods.dev/skills/boshi-xixixi/traeskill/create-github-issues-for-unmet-specification-requirements"><img src="https://agentmods.dev/badge/skills/boshi-xixixi/traeskill/create-github-issues-for-unmet-specification-requirements.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 236 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00031 $0.00236
Opus 5 $0.00015 $0.00118
Sonnet 5 $0.00006 $0.00047
Haiku 4.5 $0.00003 $0.00024

Measured 8d ago against content hash 403939f1a02b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

create-github-issues-for-unmet-specification-requirements scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.trae/Skills/.agents/skills/create-github-issues-for-unmet-specification-requirements/SKILL.md · 36 lines

What it actually says

Create GitHub Issues for Unmet Specification Requirements

Create GitHub Issues for unimplemented requirements in the specification at ${file}.

Process

  1. Analyze specification file to extract all requirements
  2. Check codebase implementation status for each requirement
  3. Search existing issues using search_issues to avoid duplicates
  4. Create new issue per unimplemented requirement using create_issue
  5. Use feature_request.yml template (fallback to default)

Requirements

  • One issue per unimplemented requirement from specification
  • Clear requirement ID and description mapping
  • Include implementation guidance and acceptance criteria
  • Verify against existing issues before creation

Issue Content

  • Title: Requirement ID and brief description
  • Description: Detailed requirement, implementation method, and context
  • Labels: feature, enhancement (as appropriate)

Implementation Check

  • Search codebase for related code patterns
  • Check related specification files in /spec/ directory
  • Verify requirement isn't partially implemented
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 8d ago First seen · 36 lines · 31 tokens per session scan A 403939f1a02b

Subscribe to this mod's changes

create-github-issues-for-unmet-specification-requirements is a skill published in the GitHub repository boshi-xixixi/TraeSkill (263 stars, last pushed 4mo ago), licensed MIT. It adds 31 tokens to every session and 236 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Related

Other skills, from other repositories

to-issues

A planning aid that breaks a PRD or technical specification into small implementation issues, each covering a complete, demonstrable piece of work.

smallnest/goal-workflow · 96 tokens

fable-orchestrate

Use when the user wants a task decomposed and driven by a Fable 5.1 orchestrator delegating implementation to Sonnet 5 workers. Fable decomposes into self-contained specs, dispatches Sonnet workers (Agents for 1–2 pieces, a Workflow for fan-out), reviews each result, merges into one branch, and takes a binding verdict…

richkuo/rk-skills · 115 tokens

fable-validate-loop

Use when the user asks to validate a GitHub issue with Fable 5.1 and then autonomously drive it to a reviewed PR in one shot — "fable-validate-loop", "fable validate and work on.

richkuo/rk-skills · 52 tokens

fable-validate-fableplan-loop

Use when the user asks to validate a GitHub issue with Fable 5.1, always plan it with Fable 5.1, and autonomously drive it to a reviewed PR in one shot — "fable-validate-fableplan-loop", "fable validate, fable plan, and work on.

richkuo/rk-skills · 74 tokens

milestoneplan

Use when the user wants a milestone's execution plan shown as a table — "milestoneplan v1", "/milestoneplan", "show the plan for v1". Read-only - reads every issue in the milestone and renders one table of issue number, description, complexity, dependencies, validate/build model and effort, fableplan, plan effort, and…

richkuo/rk-skills · 100 tokens

new-issue

Use when the user says "new issue", "create an issue", "file an issue", "/new-issue", or asks to turn a bug, idea, or discussion into a GitHub issue. Takes an optional description of what the issue should cover; with no input, derives the issue from what was discussed in the current conversation. Verifies claims…

richkuo/rk-skills · 94 tokens