brainstorming

To clarify project intent before implementation, you analyze project context and generate a structured briefing. This ensures alignment on goals, scope, and risks, reducing potential rework before any design work begins.

Project context analysis is the process of evaluating goals, scope, and risks prior to feature work. You need it before starting new design or implementation tasks to ensure shared understanding and reduce downstream rework.

To load context flows and detect expert skills, read existing contents from the ./flow/ directory and identify relevant expert-skills. This mechanism guides implementation by mapping dependencies and summarizing risks.

The best way to generate a project briefing is to summarize dependencies, risks, and user intent into a concise handoff document. This keeps flows updated and informs subsequent implementation steps effectively.

Structured brainstorming for context clarification requires no specific dependencies or components. It functions independently to analyze flows, detect expert skills, and generate briefings to guide your project alignment.

Your team needs a context briefing before designing new features to ensure alignment and reduce rework. It clarifies user intent, summarizes dependencies, and highlights risks to guide subsequent implementation steps.