Website Brief-to-Design Plan Studio
Turn an incomplete client website brief into a validated website design plan: clarify goals and audiences, define sitemap and page hierarchy, structure content, map journeys, prepare page and wireframe briefs, set conversion and accessibility requirements, and hand off a review-ready plan.
What is a Runtime Handoff?
What it does
- Create the site hierarchy and page groups from the agreed content priorities.
- Map key paths through the site for the main audience goals and conversions.
- Specify layout guidance, priority areas, and interaction notes for each page.
- Write page purpose, content blocks, and required inputs for each key page.
Give it
- The task, described in the user's own words
- Documents or written material
- Structured data or a spreadsheet
- Customer or account context
Get back
- Goal and audience summary
- Draft sitemap and page hierarchy
- User journey map
- Page briefs and wireframe notes
Understand this AI team in seconds
Get a simple explanation, see a practical example or learn exactly what to provide.
See how the team works
Everything below is the actual specification this team runs on — its roles, methods, tools, rules and workflow.
Professional workflow
What is a playbook?
What is a verifier?
Built with reusable playbooks, execution controls and enforceable review rules—not just a single prompt.
- 12 Playbooks
- Sequential workflow
- Adversarial review
- Human-gated
Agents
6What is an agent?
What is a skill?
Workflow
6What is a workflow?
- 1
Collect the brief, documents, structured data, examples, URLs, and references; create a working source map.
Brief Intake Lead - 2
Identify business goals, audiences, conversion goals, scope constraints, and content priorities from the source set.
Business and Audience Planner - 3
Turn the goals and audiences into a sitemap, page hierarchy, and the main user journeys the site must support.
Information Architect - 4
Define each key page’s purpose, content structure, conversion needs, accessibility notes, and wireframe guidance.
Page and Wireframe Planner - 5
Check the full plan for gaps, contradictions, unresolved questions, and accessibility or conversion issues.
Experience Reviewer - 6
Confirm every claim traces to supplied material, unresolved items are marked, and the handoff is ready for human approval.
Traceability and Handoff Reviewer
Tools
4What is a tool?
Rules
8What is a rule?
Every claim, recommendation, or note must be supported by supplied material or clearly marked as an open question.
Anything customer-facing, published, or sent onward must stop at the approval gate before continuation.
Do not ask for, store, or mention passwords, API keys, tokens, or other credentials.
The team may prepare plans and notes only; it must not change data in another system.
Each recommendation must carry a visible link to the source material or the assumption that supports it.
The team prepares analysis and handoff material only; a human must approve anything that leaves the process.
Never make financial, legal, publishing, or customer-facing commitments.
If evidence is missing or conflicting, mark the item as unresolved instead of settling it.
Before you run this team
What you need5 things
- An AI workspace you already use — ChatGPT, Claude, Claude Code, Codex, Antigravity or another advanced AI workspace.
- Model access and usage handled by that workspace: AigentHub provides the team structure and operating instructions, not the model.
- The inputs listed above, ready to paste or attach when you start the run.
- Optional: 4 tools this team can use — only when your workspace actually provides them.
- A person available to approve the 2 decisions this team is never allowed to take alone.
AI workspace
What it does not include
- No AI model, tokens or subscription — your AI workspace provides those.
- No hosted execution: AigentHub prepares the team, your workspace runs it.
- No automatic integrations and no credentials of any kind.
- No background monitoring, scheduled runs or unattended work.
- No external or irreversible action without a tool your workspace really provides and, where required, your approval.
It always waits for a person2 approval gates
- Never publish anything without approval
- Never send anything to a customer without approval
How it works4 steps
- 1Choose the team.
- 2Provide the task and the evidence it needs.
- 3Run the prepared instructions in your AI workspace.
- 4Review the team's final output and decide what happens next.
The AI workspace provides the model and execution environment. AigentHub provides the team structure and operating instructions.
Where you can run it6 workspaces
Best for: Documents and analysis · Strategy and decisions · Writing and structured reviews · Shorter workflows
Best for: Large files and code · Long, multi-step workflows · Real tool use · Iterative execution and the complete Runtime Handoff
Example
Example only“Convert a client website brief and supporting material into a review-ready website design plan with sitemap, page hierarchy, content structure, user journeys, page briefs, wireframe notes, and accessibility/conversion requirements.”
- Goal and audience summary
- Draft sitemap and page hierarchy
- User journey map
- Page briefs and wireframe notes
View full example
- The task, described in the user's own words
- Documents or written material
- Structured data or a spreadsheet
Website Brief-to-Design Plan Studio would then work through its workflow and hand you the artifacts above.
Illustrative example, built from this team's own declared inputs and outputs. Nothing has been run here — your AI workspace produces the actual result.
Version history
1Initial release
Reviews
0No reviews yet