Web Design Client Brief Discovery Architect

Stop quoting projects based on vague emails and messy discovery notes. This skill analyzes raw client input—transcripts, RFPs, and emails—to build a structured intelligence package before you commit to a scope or price. It identifies what you actually know versus what the client merely prefers, flags contradictions that will derail your timeline, and calculates a readiness score so you know if you are walking into a trap.

What it does

• Requirement extraction separates verified facts from client preferences, assumptions, and risks.
• Contradiction mapping highlights conflicting stakeholder requests and identifies who must resolve them.
• Readiness scoring calculates a 0-100 grade for project clarity across ten technical and business dimensions.
• Discovery blocking flags missing information that prevents accurate estimation or architectural decisions.
• Strategic translation converts vague terms like "modern" or "simple" into specific technical clarification questions.

How it works

1. Input analysis involves pasting raw notes, RFP text, or discovery transcripts into the prompt.
2. Package generation produces the full Discovery Brief, Requirements Matrix, and Scope Readiness Score.
3. Refinement allows you to request specific "modes" such as just the follow-up interview questions or the decision log.

Frameworks & tools

Works with any web project workflow including React, Next.js, Shopify, WordPress, or custom web apps. It uses a proprietary discovery framework to audit IA, SEO, UX, and functional requirements.

Why this beats prompting it yourself

Generic prompts often hallucinate missing details to make a brief look "complete." This skill is hard-coded to never invent data, instead flagging unknowns as blockers to protect your margins and timeline.

Use cases

• Pre-proposal auditing to find hidden technical risks before sending a fixed-price quote.
• Stakeholder alignment to document conflicting requirements from different client departments.
• RFP decomposition to turn a 50-page document into a lean requirements matrix and question list.
• Discovery calls to generate a prioritized list of questions that actually impact project architecture.

Known limitations

Does not produce visual designs, code, or final cost estimates. It requires at least a baseline project description to provide meaningful analysis beyond a snapshot.