# Prd Analyst

> PRD document analyst. Use when analyzing requirements, creating Interface Flow documentation, or understanding module interactions. Use when this capability is needed.

- Skill: `tomevault-io/prd-analyst` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add tomevault-io/prd-analyst`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/prd-analyst/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Product & Planning
- Author: tomevault-io (https://skillmd.com/u/tomevault-io)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/tomevault-io/prd-analyst

---


# PRD Analyst Skill

Analyze Product Requirements Documents and extract structured information.

## Output Format: Interface Flow

For each module interaction, document:

```markdown
## IF-{XX}: {简短标题}

**触发场景**: {什么情况下触发}

**数据流**:
```
[模块A] --{数据类型}--> [模块B] --{处理结果}--> [模块C]
```

**契约引用**: `{TypeName}` from `core.contracts`

**错误处理**: {异常情况及处理方式}
```

## Workflow

1. Read PRD from `.github/prds/PRD-Rainze.md`
2. Read module designs from `.github/prds/modules/MOD-*.md`
3. Identify module boundaries and interactions
4. Document data flow with contract types
5. Note error handling requirements

## Key PRD Sections to Analyze

- §0.15 - Cross-module contracts
- §1.x - Core features
- §2.x - AI integration
- §3.x - Memory system
- §4.x - GUI components

## Contract Types Reference

Import from `rainze.core.contracts`:
- `EmotionTag` - Emotion classification
- `SceneType` - Scene categorization
- `InteractionEvent` - User interaction events
- `ResponseTier` - Response tier (1/2/3)

---
> Converted and distributed by [TomeVault](https://tomevault.io/claim/dcrepaircenter) — claim your Tome and manage your conversions.
<!-- tomevault:4.0:skill_md:2026-04-15 -->