What problem does it solve? Starting a website project with a new client produces scattered, unstructured input — conversations, sketches, design exports, or nothing at all — and teams either guess at feasibility or silently drop requirements. This Skill turns that raw intake into a structured site brief where every requirement carries an explicit feasibility verdict and every cut becomes an owner-decided deferral entry. ## Core Features & Use Cases - Interview-first intake: A six-domain question bank (business, audience, content, functional, brand, measurement) used as a coverage checklist, with an exportable written form for async clients. - Per-item feasibility verdicts: Every requirement is stamped feasible-as-is, feasible-with-flip, deferred, or out-of-scope against the stack-integration-playbook's capability map. - Deferral register: A schema for recording owner decisions with context and revisit conditions, stored in the site repo. - Use Case: After a discovery call with a small business owner, run the four phases to produce a site brief where the catalog feature is marked feasible via data-layer, the customer portal is stamped out-of-scope at the documented frontier, and the missing analytics account becomes a dated deferral entry. ## Quick Start Use the client-discovery skill to run a discovery interview for a new website client and produce a feasibility-checked site brief with a deferral register.
