Prd Impact Map

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

1. Read config/service-catalog.yaml before reading the PRD. Understand what

each service owns before matching.

1. Match PRD capabilities to service description and owns fields

semantically — do not rely on keyword matching alone.

1. 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.

1. Explicitly list repos that are not affected and why — this is as

important as the affected list.

1. Mark the impact map as requiring tech lead confirmation — do not

treat it as authoritative without LGTM.

Inputs

1. PRD — (REQUIRED) prd/INIT-{id}.md in -meta
2. Service catalog — (REQUIRED) config/service-catalog.yaml in -meta
3. Meta PRD PR body — (OPTIONAL) PM's description of initiative scope

Process

1. T0 Gather — PRD + service-catalog.yaml
2. T1 Understand — list PRD capability areas (data flows, user actions,

integrations, storage, auth, notifications, etc.)

1. T2 Match — for each capability, match to service description + owns;

include transitive via depends_on

1. T3 Order — derive build/merge order from depends_on graph
2. T4 Output — produce impact map comment body
3. T5 Post — add as PR comment on the open meta PRD PR

Output format

Post as a PR comment on the meta PRD PR (not committed as a file).

## Impact map — {INIT-id}
_Generated by /prd-impact-map — {date}_

### Affected services

| Service | Repo | Why | Team | Spec to create |
|---------|------|-----|------|---------------|
| {name} | {org}/{repo} | {capability matched} | @{org}/{team} | INIT-{id}-{slug}.md |

### Transitively affected (via depends_on)

| Service | Depends on | Potential impact |
|---------|-----------|-----------------|

### Not affected

| Service | Reason |
|---------|--------|

### Suggested merge/build order
{repo-A} → {repo-B} → {repo-C}

### Confidence
| Match | Confidence | Notes |
|-------|-----------|-------|
| {service} | High/Medium/Low | {rationale} |

---
**@{tech-lead}** — please confirm or correct before engineering opens spec PRs.
Review deadline: 2 business days.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: drivestream-lab
• Source: drivestream-lab/prayog-skills
• License: MIT

Install and usage instructions live in the source repository linked above.