lgwanai How it works:
- Load prior context (PROJECT.md, REQUIREMENTS.md, STATE.md, prior CONTEXT.md files)
- Scout codebase for reusable assets and patterns
- Analyze phase — skip gray areas already decided in prior phases
- Present remaining gray areas — user selects which to discuss
- Deep-dive each selected area until satisfied
- Create CONTEXT.md with decisions that guide research and planning
Output: {phase_num}-CONTEXT.md — decisions clear enough that downstream agents can act without asking the user again
Context files are resolved in-workflow using init phase-op and roadmap/state tool calls.
If --assumptions is in $ARGUMENTS:
Read and execute $HOME/.claude/get-shit-done/workflows/list-phase-assumptions.md end-to-end.
Stop here.
Otherwise, if DISCUSS_MODE is "assumptions":
Read and execute $HOME/.claude/get-shit-done/workflows/discuss-phase-assumptions.md end-to-end.
Otherwise ("discuss" / unset / any other value):
Read and execute $HOME/.claude/get-shit-done/workflows/discuss-phase.md end-to-end.
MANDATORY: Read the appropriate workflow file BEFORE taking any action. The objective and success_criteria sections in this command file are summaries — the workflow file contains the complete step-by-step process with all required behaviors, config checks, and interaction patterns. Do not improvise from the summary.
Lazy loading: templates/context.md is loaded inside the write_context step of the active workflow. discuss-phase-power.md is loaded inside discuss-phase.md when --power is detected. Do not load either here.