approve-brief

To gate a project brief from draft to approved, the pipeline validates completion of all 13 brief sections, updates the session-state, and appends audit logs to ensure traceability before transitioning the brief to BRIEF_APPROVED.

Incomplete project briefs fail the quality gate and the pipeline refuses to transition them from BRIEF_DRAFT to BRIEF_APPROVED if the 13 sections are missing or still contain placeholders.

Yes, approving a project brief requires access to the session-memory/SESSION-STATE.md file and the brief HTML located at scope-of-work/<slug>-project-brief.html to validate and unlock the next pipeline steps.

Approving a brief transitions the pipeline stage to BRIEF_APPROVED, which immediately unlocks the /build-scope-of-work command and reveals other valid downstream commands to continue the project workflow.

Yes, the brief quality gate allows sections to be marked as TBD, but it will strictly refuse approval if any of the 13 required sections are entirely missing or still contain unaddressed placeholders.

Audit logging is important when locking project briefs because it appends traceability records to the session-state, ensuring reliable tracking of the BRIEF_DRAFT to BRIEF_APPROVED transition for project management compliance.