harness-brief

To create a project brief from a vague idea, use guided Socratic questioning to surface requirements and constraints, then generate a structured PROJECT_BRIEF.md. This process works for both greenfield and existing projects by loading ambient context.

A PROJECT_BRIEF.md is a canonical document with six required sections that converts ideas into executable plans. You need one to start a pipeline with a clear, role-aligned plan and ensure all team members understand project constraints.

Yes, the project brief generator works with existing codebases by loading ambient context from the .harness/PROJECT_BRIEF.md file and available project files. This ensures the generated brief improves relevance and aligns with current project state.

To generate a .harness/PROJECT_BRIEF.md, run the guided brief generator which loads brainstorming context, asks clarifying questions, writes the brief with exact headings, and provides handoff instructions while ensuring the .harness/ directory exists.

The best way to structure a project brief is using a standardized format with six required sections generated through guided questioning. This standardization enables teams to start pipelines with precise, role-aligned plans rather than ad-hoc documentation.

Your project planning lacks an executable plan because vague ideas have not been converted into a precise PROJECT_BRIEF.md. Using a guided generator to establish role-aligned plans and standard sections resolves this ambiguity.