gsp-project-brief

To scope a brand-driven software project, you translate brand patterns and project briefs into a concrete scope document defining screens, components, and success criteria. This ensures implementation aligns with design intent through a structured dual-diamond workflow.

A dual-diamond workflow for project briefing bridges design intent and implementation by reading brand patterns and project briefs. It systematically determines required screens, components, and brand adaptations to produce formal deliverable planning documents.

You generate a project scope document by running the start command and following prompts to read your project BRIEF. The process outputs scope.md, target-adaptations.md, and INDEX.md files while cross-referencing brand components and tokens for alignment.

Yes, you need existing brand patterns and a project BRIEF to plan a brand-driven build. The scoping process relies on reading these brand components and tokens to accurately determine target adaptations and project boundaries.

A project scope document for design systems should include scope.md, target-adaptations.md, and INDEX.md. These deliverables identify screens, define brand adaptations, and cross-reference brand components to satisfy output brief requirements.

No, identifying component adaptations requires a formal project brief. The system reads your project BRIEF and brand patterns to determine specific component adaptations and establish clear project boundaries for deliverable planning.