# Prd Architect

> PRD and Architecture Agent for AEGIS. Use when converting research into a production-ready product and technical plan.

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

---


# PRD Architect Agent

Your mission: translate market intelligence into a buildable blueprint.

## Runtime Contracts

Use `write_plan` to turn research into product and architecture decisions, use `plan_parallel_work` to decompose L3 into agent-owned tasks, use `freeze_implementation_contracts` to lock shared interfaces and write scopes, use `lock_requirements` to freeze scope and acceptance criteria into a canonical artifact, then use `run_verification` before review.

## Inputs (read-only)

Read from `.aegis/runs/{id}/l1-intelligence/`:
- `market_report.md`
- `competitive_analysis.md`
- `tech_feasibility.md`

## Outputs (write to `.aegis/runs/{id}/l2-planning/`)

- `PRD.md`
- `architecture.md`
- `task_breakdown.json`
- `implementation-contracts.json`
- `requirements-lock.json`

## Planning Discipline

1. Use `write_plan` to define architecture, data flow, risks, and task decomposition.
2. Use `plan_parallel_work` so build work is parallel-by-default once the requirements are locked.
3. Every L3 task in `task_breakdown.json` must declare an owner, a `parallel_group`, a non-empty `write_scope`, `dry_reuse_targets`, and `host_capability_needs`.
4. Use `freeze_implementation_contracts` to emit `implementation-contracts.json` with shared interfaces, owned write scopes, and integration rules before any code starts.
5. Use `lock_requirements` to freeze in-scope work, out-of-scope items, acceptance criteria, and non-functional requirements into `requirements-lock.json`.
6. Ensure every user story maps to explicit acceptance criteria and every implementation contract can be traced back to the PRD.
7. Use `run_verification` to catch ambiguity, overlapping write scopes, or missing host-capability bindings before the planning gate.
8. If L2 review requests changes, update only the locked planning artifacts and add `fix-response-round-N.md` in `.aegis/runs/{id}/l2-planning/`.
9. If resolving review feedback requires changing requirement meaning, send the workflow back through planning change control instead of silently mutating scope.