advise-project-direction

Independent project-direction advice evaluates purpose, goals, progress, decisions, and boundaries before execution. It classifies ideas into current-path, branch-first, new-project, research-first, or defer stances, returning clear next-step actions and verification gates to prevent scope creep.

Assessing branching choices and risk mitigation requires an independent advisory workflow that rechecks core project materials like instruction files, READMEs, and decision logs. This returns a structured classification of whether to branch, proceed, or defer with actionable next steps.

Yes, providing access to core project materials including instruction files, READMEs, and decision logs is required. These documents provide the necessary context to refresh the project state and deliver accurate project-direction guidance and scope assessment.

An advisory workflow classifies ideas into five stances: current-path, branch-first, new-project, research-first, or defer. It evaluates project boundaries and progress, then outputs a clear decision stance accompanied by next-step actions and verification gates.

Yes, this approach is specifically applicable to non-executor advisory roles in product management. It supports product strategy decisions, scope assessment, branching choices, and risk mitigation by providing independent guidance without directly executing the project tasks.

You should defer a project decision when the advisory workflow determines that current goals, progress, or boundaries lack sufficient clarity for action. Deferring is chosen over current-path or branch-first paths when research-first is also inadequate to mitigate execution risks.