multilingual-absa / .opencode /command /gsd-discuss-phase.md
Aryan Mishra
feat: initial commit - Multilingual ABSA project setup with 6 phases, 36 requirements
a6b96c2
|
Raw
History Blame Contribute Delete
4.3 kB

A newer version of the Gradio SDK is available: 6.26.0

Upgrade
metadata
description: Gather phase context through adaptive questioning before planning.
argument-hint: >-
  <phase> [--all] [--auto] [--chain] [--batch] [--analyze] [--text] [--power]
  [--assumptions]
requires:
  - config
  - phase
tools:
  read: true
  write: true
  bash: true
  glob: true
  grep: true
  question: true
  agent: true
  mcp__context7__resolve-library-id: true
  mcp__context7__query-docs: true
Extract implementation decisions that downstream agents need β€” researcher and planner will use CONTEXT.md to know what to investigate and what choices are locked.

How it works:

  1. Load prior context (PROJECT.md, REQUIREMENTS.md, STATE.md, prior CONTEXT.md files)
  2. Scout codebase for reusable assets and patterns
  3. Analyze phase β€” skip gray areas already decided in prior phases
  4. Present remaining gray areas β€” user selects which to discuss
  5. Deep-dive each selected area until satisfied
  6. 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

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. **Copilot (VS Code):** Use `vscode_askquestions` wherever this workflow calls `question`. They are equivalent β€” `vscode_askquestions` is the VS Code Copilot implementation of the same interactive question API. Phase number: $ARGUMENTS (required)

Context files are resolved in-workflow using init phase-op and roadmap/state tool calls.

**Mode routing:** ```bash _GSD_SHIM_NAME="gsd-tools.cjs"; _GSD_RUNTIME_ROOT="${RUNTIME_DIR:-$(git rev-parse --show-toplevel 2>/dev/null || pwd)}"; GSD_TOOLS="${_GSD_RUNTIME_ROOT}/gsd-core/bin/${_GSD_SHIM_NAME}"; if [ -f "$GSD_TOOLS" ]; then gsd_run() { node "$GSD_TOOLS" "$@"; }; elif [ -f "${_GSD_RUNTIME_ROOT}/.claude/gsd-core/bin/${_GSD_SHIM_NAME}" ]; then GSD_TOOLS="${_GSD_RUNTIME_ROOT}/.claude/gsd-core/bin/${_GSD_SHIM_NAME}"; gsd_run() { node "$GSD_TOOLS" "$@"; }; elif command -v gsd-tools >/dev/null 2>&1; then GSD_TOOLS="$(command -v gsd-tools)"; gsd_run() { "$GSD_TOOLS" "$@"; }; elif [ -f "/Users/theogengineer/Projects/Multilingual-Absa/.opencode/gsd-core/bin/${_GSD_SHIM_NAME}" ]; then GSD_TOOLS="/Users/theogengineer/Projects/Multilingual-Absa/.opencode/gsd-core/bin/${_GSD_SHIM_NAME}"; gsd_run() { node "$GSD_TOOLS" "$@"; }; else echo "ERROR: gsd-tools.cjs not found at $GSD_TOOLS and gsd-tools is not on PATH. Run: npx -y @opengsd/gsd-core@latest --claude --local" >&2; exit 1; fi DISCUSS_MODE=$(gsd_run query config-get workflow.discuss_mode 2>/dev/null || echo "discuss") ```

If --assumptions is in $ARGUMENTS: Read and execute /Users/theogengineer/Projects/Multilingual-Absa/.opencode/gsd-core/workflows/list-phase-assumptions.md end-to-end. Stop here.

Otherwise, if DISCUSS_MODE is "assumptions": Read and execute /Users/theogengineer/Projects/Multilingual-Absa/.opencode/gsd-core/workflows/discuss-phase-assumptions.md end-to-end.

Otherwise ("discuss" / unset / any other value): Read and execute /Users/theogengineer/Projects/Multilingual-Absa/.opencode/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.

- Prior context loaded and applied (no re-asking decided questions) - Gray areas identified through intelligent analysis - User chose which areas to discuss - Each selected area explored until satisfied - Scope creep redirected to deferred ideas - CONTEXT.md captures decisions, not vague vision - User knows next steps