init-client-brief

To create a validated client brief JSON, run the intake command with a client slug and follow the guided prompts to collect blank fields, which automatically validates against the site-brief schema and outputs to the client's site directory.

Automating site brief intake is done by guiding users through Groups A-F to collect only blank fields, validating the output against the site-brief schema, and producing a canonical JSON brief for reproducible setup.

Yes, you can use this brief intake workflow for deterministic planning handoffs because it produces a canonical JSON file that directly satisfies downstream validation and site planning workflows.

Yes, you need a site-brief schema to validate client intake fields, as the workflow checks the collected JSON against schemas/site-brief.schema.json to ensure deterministic outputs before planning.

After generating a site brief JSON, the next steps are to run validate-brief to check the schema and then plan-site to transition the client engagement from intake to the planning stage.

Client brief validation fails during project onboarding when the collected JSON does not match the required site-brief schema, so the guided intake ensures all blank fields are populated correctly before handoff.