# Prd Ia Checklist Review

> Use when creating or reviewing PRD, IA, screen inventory, or feature inventory from requirements documents and the user wants completeness, traceability, or no missing requirements. Build a PRD-based checklist first, then review IA/screens/features against it, and record statuses like 반영, 부분반영, 미반영, 재검토 before treating the document as complete.

- Skill: `kim-dh2417/prd-ia-checklist-review` (Agent Skill)
- Install (CLI): `npx skillmds@latest add kim-dh2417/prd-ia-checklist-review`
- Raw SKILL.md: https://api.skillmd.com/api/skills/kim-dh2417/prd-ia-checklist-review/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Product & Planning
- Author: kim-dh2417 (https://skillmd.com/u/kim-dh2417)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/kim-dh2417/prd-ia-checklist-review

---


# PRD IA Checklist Review

Use this skill when the task is not just to draft PRD or IA, but to ensure nothing is missing.

## Workflow

1. Identify the source-of-truth documents.
Usually this is:
- requirements or RFP text
- PRD drafts
- feature inventory
- IA tree
- screen inventory

2. Build a checklist before finalizing IA or PRD.
The checklist should be derived from PRD or the closest requirements source and should contain:
- feature or requirement item
- source reference
- target document being reviewed
- status
- notes

3. Use these statuses consistently:
- `반영`
- `부분반영`
- `미반영`
- `재검토`

4. Review in this order unless the user requests otherwise:
- feature inventory
- IA
- screen inventory

5. Do not treat a draft as final until the checklist comparison is done.

## PRD Review Pattern

When reviewing PRD completeness:
- derive the checklist from requirements text or source modules
- verify each business goal, problem, module, requirement class, and nonfunctional constraint appears in the PRD
- mark missing or weakly represented items explicitly

## IA Review Pattern

When reviewing IA completeness:
- derive the checklist from PRD or feature inventory
- compare each item against:
  - IA menu placement
  - screen coverage
  - cross-cutting operational or control placement
- record whether it is reflected clearly

## Output Documents

Preferred output set:
- `01_feature_inventory.md`
- `02_information_architecture.md`
- `03_screen_inventory.md`
- `04_ia_review_checklist.md`

If reviewing PRD first, add:
- `requirements-traceability.md`

## Review Rules

- Prefer traceability over elegance in early drafts.
- Preserve source wording when it helps avoid omission.
- Treat `관리` style source items as needing explicit review for likely sub-functions such as 조회, 상세, 등록, 수정, 승인, 이력, 설정.
- Do not invent new business capabilities. If a screen/function is inferred structurally, note that it is a structured derivation from the source rather than a new requirement.
- When a checklist row is only partially represented in IA, keep it as `부분반영` and propose what screen or menu is missing.

## Completion Criteria

A PRD or IA draft is not considered complete until:
- a checklist exists
- all major requirement areas are reviewed
- `미반영` and `부분반영` items are visible
- the reviewer can trace menu/screen/function items back to source requirements