A workflow for turning a plan, specification, or product requirements document into separate issues in a project's issue tracker. Each issue describes a small end-to-end change rather than only one technical layer.

Use it to create implementation tickets from a plan, inspect a referenced issue, explore the codebase, and divide work into independently deliverable vertical slices.

It removes the need to manually divide broad work into tasks that different developers can pick up independently. It also uses the project's existing terminology and context when available.

How jd-solanki/airig configures Claude Code and Codex

Reuse

Borrowing it

Nothing to install: this file belongs to jd-solanki/airig. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/jd-solanki/airig/main/.ai/skills/to-issues/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/jd-solanki/airig

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/jd-solanki/airig/to-issues/github.svg)](https://agentmods.dev/skills/jd-solanki/airig/to-issues)

Your own site

<a href="https://agentmods.dev/skills/jd-solanki/airig/to-issues"><img src="https://agentmods.dev/badge/skills/jd-solanki/airig/to-issues/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/jd-solanki/airig/to-issues"><img src="https://agentmods.dev/badge/skills/jd-solanki/airig/to-issues.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 53 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,371 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.

Model	Per session	Once invoked
Fable 5.1	$0.00053	$0.01371
Opus 5.5	$0.00021	$0.00548
Sonnet 5.5	$0.00011	$0.00274
Haiku 4.5	$0.00005	$0.00137

Measured 1mo ago against content hash 4ddd564fd88b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

to-issues 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 1mo 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.

.ai/skills/to-issues/SKILL.md · 101 lines

How it starts

The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.

To Issues

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

Invoke the github-labels skill before publishing so each generated issue gets the correct GitHub labels.

The issue tracker and triage label vocabulary should have been provided to you — run /setup-matt-pocock-skills if not.

Process

1. Gather context

Work from whatever is already in the conversation context. If the user passes an issue reference (issue number, URL, or path) as an argument, fetch it from the issue tracker and read its full body and comments.

2. Explore the codebase (optional)

If you have not already explored the codebase, do so to understand the current state of the code. Issue titles and descriptions should use the project's domain glossary vocabulary, and respect ADRs in the area you're touching.

Look for opportunities to prefactor the code to make the implementation easier. "Make the change easy, then make the easy change."

3. Draft vertical slices

Break the plan into tracer bullet issues. Each issue is a thin vertical slice that cuts through ALL integration layers end-to-end, NOT a horizontal slice of one layer.

Slices may be 'HITL' or 'AFK'. HITL slices require human interaction, such as an architectural decision or a design review. AFK slices can be implemented and merged without human interaction. Prefer AFK over HITL where possible.

4. Quiz the user

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

Title: conventional commit title — type(scope): short imperative description
- type: feat, fix, refactor, perf, docs, test, chore, ci, style, build
- scope: the module, package, or domain area (e.g. auth, cli, api, ui, db) — lowercase
- ! after type/scope for breaking changes: feat!(auth): … or refactor(api)!: …
- description: lowercase, imperative mood, no trailing period
- Examples: feat(auth): add OAuth2 login, fix(cli): handle missing config, refactor!(api): remove legacy endpoints
Blocked by: which other slices (if any) must complete first
User stories covered: which user stories this addresses (if the source material has them)

Read the full file on GitHub · 101 lines

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.

1mo ago First seen · 101 lines · 53 tokens per session scan A 4ddd564fd88b

Subscribe to this mod's changes

to-issues is a skill published in the GitHub repository jd-solanki/airig (2 stars, last pushed 3mo ago), licensed MIT. It adds 53 tokens to every session and 1,371 once invoked, about $0.0002 per session on Opus 5.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-08-31.

Project management

story-readiness

Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.

Donchitos/Claude-Code-Game-Studios · 48 tokens

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

qa-project-bootstrap

Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…

petrkindlmann/qa-skills · 124 tokens

remove

Remove a deployed framework or addon from the current workspace.

jmagly/aiwg · 12 tokens

airig: Skill for Claude Code