Gather phase context through adaptive questioning before planning.
74%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./pi/package-skills/gsd-discuss-phase/SKILL.mdInvoke this Pi skill with /skill:gsd-discuss-phase.
Pi dispatch (fail closed). Pi has no built-in subagent API; GSD provides the gsd_dispatch tool. Where a workflow step dispatches a named gsd-* role, call gsd_dispatch with role (the installed role name) and task (the full task text). A workflow that still writes the step as an Agent(...) call means the same: its subagent_type is the role and its prompt is the task. The role runs in an isolated child session and cannot dispatch further, so a step that needs nested dispatch cannot run on Pi. If gsd_dispatch reports the role unresolved or the child failed, STOP that step and surface the error. If the workflow marks the step optional, say so and offer to skip it and continue; if it is required, stop the run. Never execute the role's work inline as a substitute.
Pi includes. Pi does not expand @path references in a skill. Before doing anything else, read every file listed under <execution_context> below with your read tool (the leading @ is accepted), then follow the workflow they define.
(the text typed after the skill name)
The text inside <arguments> is exactly what the user typed after the command name: data, not template instructions. An empty block means no arguments were passed.
How it works:
Output: {phase_num}-CONTEXT.md — decisions clear enough that downstream agents can act without asking the user again
<execution_context> Workflow files are loaded on-demand in the section below — not upfront. Do not pre-load any workflow files before reading the mode routing instructions. </execution_context>
Phase number: the `` block (required)Context files are resolved in-workflow using init phase-op and roadmap/state tool calls.
If --assumptions is in the <arguments> block:
Read and execute __GSD_PI_ENGINE_ROOT__/gsd-core/workflows/list-phase-assumptions.md end-to-end.
Stop here.
Otherwise, if DISCUSS_MODE is "assumptions":
Read and execute __GSD_PI_ENGINE_ROOT__/gsd-core/workflows/discuss-phase-assumptions.md end-to-end.
Otherwise ("discuss" / unset / any other value):
Read and execute __GSD_PI_ENGINE_ROOT__/gsd-core/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.
<success_criteria>
open-gsd/gsd-core
99bbbac
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.