.agents/skills/gsd-discuss-phase/SKILL.md
Gather phase context through adaptive questioning before planning. Use --auto to skip interactive questions (the agent picks recommended defaults).
npx skillsauth add scaixeta/CindyAgent gsd-discuss-phaseInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
How it works:
Output: {phase_num}-CONTEXT.md — decisions clear enough that downstream agents can act without asking the user again
</objective>
<execution_context> @.agents/get-shit-done/workflows/discuss-phase.md @.agents/get-shit-done/workflows/discuss-phase-assumptions.md @.agents/get-shit-done/templates/context.md </execution_context>
<context> Phase number: $ARGUMENTS (required)Context files are resolved in-workflow using init phase-op and roadmap/state tool calls.
</context>
If DISCUSS_MODE is "assumptions": Read and execute @.agents/get-shit-done/workflows/discuss-phase-assumptions.md end-to-end.
If DISCUSS_MODE is "discuss" (or unset, or any other value): Read and execute @.agents/get-shit-done/workflows/discuss-phase.md end-to-end.
MANDATORY: The execution_context files listed above ARE the instructions. Read the 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. </process>
<success_criteria>
data-ai
Post-mortem investigation for failed GSD workflows — analyzes git history, artifacts, and state to diagnose what went wrong
data-ai
Execute a trivial task inline — no subagents, no planning overhead
tools
Execute all plans in a phase with wave-based parallelization
tools
Route freeform text to the right GSD command automatically