What is prd-impact-map?

A planning tool that reads a product requirements document (PRD) and a service catalogue to identify which code repositories may be affected.

Use it to trace requirements through service ownership and dependency chains, save a versioned impact-map report, and prepare a handoff for a pull request.

It gives the technical lead a clear impact map before engineers open specification changes in individual repositories. It also shows which repositories are not affected and why.

prd-impact-map — Skill for Claude Code by drivestream-lab

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 drivestream-lab/prayog-skills --skill prd-impact-map

Clone the repo

git clone --depth 1 https://github.com/drivestream-lab/prayog-skills

Made for: Claude Code.

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/drivestream-lab/prayog-skills/prd-impact-map/github.svg)](https://agentmods.dev/skills/drivestream-lab/prayog-skills/prd-impact-map)

Your own site

<a href="https://agentmods.dev/skills/drivestream-lab/prayog-skills/prd-impact-map"><img src="https://agentmods.dev/badge/skills/drivestream-lab/prayog-skills/prd-impact-map/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/drivestream-lab/prayog-skills/prd-impact-map"><img src="https://agentmods.dev/badge/skills/drivestream-lab/prayog-skills/prd-impact-map.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 3,241 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.00108	$0.03241
Opus 5	$0.00054	$0.01621
Sonnet 5	$0.00022	$0.00648
Haiku 4.5	$0.00011	$0.00324

Measured 12d ago against content hash 76d5a5a09a0e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

prd-impact-map 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 12d 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.

skills/requirements/prd-impact-map/SKILL.md · 266 lines

How it starts

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

PRD impact map

Identify which repos are affected by a PRD and produce an impact map for tech lead confirmation. Do not open spec PRs in app repos — engineering opens those after tech lead confirms the map.

NON-NEGOTIABLE

Resolve one service catalog under <client>-meta/config/ before reading the PRD. Prefer service-catalog-<org>.yaml when org is known (unique governance-<org>.yaml suffix). Otherwise accept exactly one of service-catalog.yaml or service-catalog-*.yaml. Fail closed on zero or multiple matches. Do not merge catalogs. Never hardcode a tenant org. Understand what each service owns before matching.
Match PRD capabilities to service description and owns fields semantically — do not rely on keyword matching alone.
Include transitively affected repos via depends_on chains. If repo B depends on repo A and the PRD touches A, flag B as potentially affected.
Explicitly list repos that are not affected and why — this is as important as the affected list.
Save the canonical map at reports_dir/Impact-Map-{INIT-id}.md. A PR comment or label is never the source of truth. Never write Impact-Map-*-revN.md / *-v2 siblings — overwrite the canonical path and bump map_revision (see prayog-skills/references/artifact-write-contract.md).
Increment map_revision for every changed map and record the prior revision plus change reason. Do not edit history to make a revision appear unchanged. If a legacy *-revN sibling exists, migrate into the canonical path and stop writing the sibling (purge siblings only via /purge-initiative-artifacts-meta allowlist — Impact-Map is KEEP).
Mint durable identities H1–H3 per prayog-skills/references/artifact-write-contract.md: H1 source_prd_digest (PRD bytes), H2 one scope_digest per affected repo (canonical payload recipe), H3 map_revision. Prefer CAP-* / REQ-* in capability lists (legacy free-text or FR-* acceptable until next PRD edit — see prayog-skills/references/id-conventions.md). A tech-lead approval (G1) is valid only for the exact meta PR head SHA carrying those values. Impact-Map is KEEP through initiative-closure purge; do not treat mid-lane app report digests as map identity.
Treat impact-map-* labels as projections. If artifact, review, and label disagree, the gate is closed.
A material PRD/map change or tech-lead revocation invalidates approval. Produce a downstream ripple action for every repo already in flight.
No forge mutations in this skill. Do not create a branch, commit, push, PR, comment, review request, or label here. Fill handoff.forge for open_draft_pr and recommend /open-draft-pr (or orchestrator ForgeClient on prd-pr-action). See prayog-skills/references/forge-side-effects.md#content-producers.
Gate labels are a visible workflow projection, not authority. Exactly one PE gate label may be active: impact-map-pending, impact-map-lgtm, or impact-map-blocked. impact-map-revised and impact-map-stale are additional invalidation labels and always close the gate.

Read the full file on GitHub · 266 lines

Files

What ships with it

5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

12d ago First seen · 266 lines · 108 tokens per session scan A 76d5a5a09a0e

Subscribe to this mod's changes

prd-impact-map is a skill published in the GitHub repository drivestream-lab/prayog-skills (2 stars, last pushed 4d ago), licensed MIT. It adds 108 tokens to every session and 3,241 once invoked, about $0.0005 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-08-31.

Planning

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens