Write or narrowly repair one decision-focused HLD from an approved PRD, maintained architecture context, and confirmed technical decisions in plain, skimmable technical English.
Write or narrowly repair one buildable repository LLD from an approved HLD, confirmed repo decisions, and bounded code evidence, including an implementation-complete data model and a frontend-ready API/client contract in concise, skimmable technical English.
Produce a concise, decision-focused high-level design (HLD) for a feature. Ground the direction in requirements and the existing system, record only material trade-offs, and write a developer-readable hld.md. Read-only except for the HLD and open-question…
Write or repair one final PRD from fully confirmed structured context in plain, skimmable technical English. Use only after the PRD interview is complete; never invent missing product decisions.
Produce a concise, buildable low-level design (LLD) for one repository. Ground it in that repo's code, show the implementation seam, responsibilities, critical flows, interfaces, state, and verification without repeating the HLD or padding irrelevant…
Convert legacy PRD and HLD documents into current concise structures while preserving every existing decision and adding no new product or architecture content.
Apply human-approved corrections to final design-document copies with minimal, validated edits and no unrelated rewriting.
Clarify material architecture decisions before an HLD is finalized. Generate feature-specific technical Grill questions, audit prior answers and contradictions, and collect grouped answers without drafting design prose.