Webcraft brief

Produce a brief that supports decisions about pages, content, and design without inventing business facts.

Start or resume

Read 00-project.md and the current brief in the project's artifact directory, default docs/webcraft/. If setup is missing, direct the user to /webcraft-init; do not run it silently. A setup blocker unrelated to brief writing may remain recorded while the user works on the brief.

Create when absent, resume a draft, or revise the parts affected by new instructions or material. If the brief is ready and the user supplied no change, ask what to add or reconsider. Use a question tool when available. Preserve unrelated decisions; do not restart an interview already answered by the conversation or sources.

An explicit restart may rework this stage; preserve its prior milestone through existing history or a scoped snapshot. Approval belongs to a specific revision and does not automatically carry over to substantive edits.

Develop the brief

Read supplied material and inspect relevant existing content. Distinguish confirmed facts, user preferences, working assumptions, and unresolved claims. Resolve contradictions that change the site's purpose or promises rather than merging incompatible statements.

Capture shared audience motivations, objections, known acquisition context, and actual customer language from available product-marketing research, interviews, reviews, or support material. Link sources and distinguish quotations from paraphrases and assumptions. Do not require new research when the supplied evidence is enough to proceed; record consequential gaps for later decisions.

Collect existing brand colors, typography, logos, guidelines, and links to any component/design library not found during init. Ask about brand color only if not already established. Record exact supplied values and whether they are fixed brand requirements or flexible preferences; leave accessible UI palette derivation to direction.