danthamanvoiss Purpose
Build website design requirements brief covering objectives, IA, UX constraints, and conversion goals.
Use when
- A web project needs requirements definition before any wireframing or prompt-spec generation.
- You are gathering scope and constraints, not generating visual prompts yet.
Required inputs
- Project goals, audience, and page scope [client-provided].
- Brand/client context from context/BRAND-CONTEXT.template.md and context/CLIENT-CONTEXT.template.md.
- Technical constraints, accessibility requirements, and content dependencies.
Safety/authority
- No fabricated user research, analytics, or technical capabilities.
- No direct site changes; produce brief draft only.
- Flag unknown requirements explicitly for stakeholder confirmation.
Workflow
- Define business/user goals and success criteria.
- Map page inventory, information hierarchy, and conversion flows.
- Document constraints (brand, accessibility, platform, timeline).
- Produce implementation-ready web brief with open questions.
Output format
- Web design brief summary
- IA and page-scope table
- Constraint and dependency list
- Open questions / approvals needed
Quality checks
- Brief is requirements-focused and distinct from UI prompt specification tasks.
- Scope boundaries and acceptance criteria are explicit.
Related skills
landing-page-wireframe-draft, superdesign-ui-prompt-adapter, creative-brief-generator