airig: Skill for Claude Code

.ai/skills/to-prd/SKILL.md

to-prd is a skill for Claude Code, Codex from jd-solanki/airig. It costs 36 tokens per session (901 once invoked), scanned A, original, MIT.

A workflow that turns the current conversation and codebase context into a product requirements document, or PRD—a written plan for what to build and how to implement it. It publishes the PRD to the project's issue tracker and creates follow-up implementation issues.

In plain words
What is it for?
Use it to explore the repository, define testing points, write the PRD, apply the required GitHub labels, and publish the parent issue with implementation work beneath it.
Why use it?
It turns scattered discussion into a structured, trackable plan without requiring a separate user interview. It also connects the product plan to the project's issue workflow.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

This is jd-solanki/airig's own configuration. It tells Claude Code and Codex how to work on airig itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything airig configures →

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-prd/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.

agentmods badge for to-prd

README.md
[![agentmods](https://agentmods.dev/badge/skills/jd-solanki/airig/to-prd/github.svg)](https://agentmods.dev/skills/jd-solanki/airig/to-prd)
Your own site
<a href="https://agentmods.dev/skills/jd-solanki/airig/to-prd"><img src="https://agentmods.dev/badge/skills/jd-solanki/airig/to-prd/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 to-prd

Your own site · 80×15
<a href="https://agentmods.dev/skills/jd-solanki/airig/to-prd"><img src="https://agentmods.dev/badge/skills/jd-solanki/airig/to-prd.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 36 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 901 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.00036 $0.00901
Opus 5.5 $0.00014 $0.00360
Sonnet 5.5 $0.00007 $0.00180
Haiku 4.5 $0.00004 $0.00090

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

Security

Grade A, and why

to-prd 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-prd/SKILL.md · 90 lines

How it starts

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

This skill takes the current conversation context and codebase understanding and produces a PRD. Do NOT interview the user — just synthesize what you already know.

A PRD is a Parent Target Issue whose body is a product and implementation plan: krutrimbox discovers it (when it is labeled ready-for-agent and has no parent) and walks the Implementation Issues that the follow-up to-issues workflow creates as its native sub-issues.

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

Process

  1. Explore the repo to understand the current state of the codebase, if you haven't already. Use the project's domain glossary vocabulary throughout the PRD, and respect any ADRs in the area you're touching.

  2. Sketch out the seams at which you're going to test the feature. Existing seams should be preferred to new ones. Use the highest seam possible. If new seams are needed, propose them at the highest point you can. The fewer seams across the codebase, the better - the ideal number is one.

Check with the user that these seams match their expectations.

  1. Write the PRD using the template below, then publish it to the project issue tracker. Apply needs-triage. Do not apply ready-for-agent yet; a Parent Target Issue becomes ready only after the follow-up to-issues workflow has created and linked all its Implementation Issues, at which point to-issues applies ready-for-agent to the PRD.

Issue title format — follow Conventional Commits:

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) — keep it short and lowercase
  • ! after type/scope signals a breaking change: 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

Read the full file on GitHub · 90 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.

  1. 1mo ago First seen · 90 lines · 36 tokens per session scan A 296b8d37b82f

Subscribe to this mod's changes

to-prd is a skill published in the GitHub repository jd-solanki/airig (2 stars, last pushed 3mo ago), licensed MIT. It adds 36 tokens to every session and 901 once invoked, about $0.0001 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.