Engagement Scoping

Produce the keystone deliverable of a cogni-consult engagement: one SMART key question, five scoping dimensions, and 3-6 action fields declared as the work-breakdown structure every later skill works inside. The method itself — SMART table, dimension prompts, output template, quality signals — lives in $CLAUDE_PLUGIN_ROOT/references/methods/scope-dimensions.md; this skill owns the conversation flow and the state writes.

Workflow

1. Prerequisite Gate

When arriving via an in-session consult-setup handoff, the engagement directory is already known — skip discovery. Otherwise locate the engagement:

bash $CLAUDE_PLUGIN_ROOT/scripts/discover-projects.sh --json

and confirm the intended engagement with the user when more than one is registered. When discovery returns zero engagements, treat it the same as a missing consult-project.json — redirect to consult-setup as below.

Read <engagement-dir>/consult-project.json. If it is missing, redirect: "There's no engagement yet — let's run consult-setup first to scaffold one." Then dispatch Skill("cogni-consult:consult-setup") and stop — write nothing. The same Read supplies everything this skill needs (name, language, workflow_state.scope) and anchors the later Edit calls.

When workflow_state.scope is already complete, this is a re-scope (pivot): confirm with the consultant before proceeding, and follow the re-run guard in step 4.