agentsclimarketplace

Cds discuss phase

Skill Enakoneschniy/claude-dev-stack/vendor/cds-workflow/skills/cds-discuss-phase

One command to set up a complete AI-powered development workflow with Claude Code. Persistent memory, session management, 35+ CLI tools.

Install
npx -y skills add Enakoneschniy/claude-dev-stack --skill cds-discuss-phase

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Gather phase context through adaptive questioning before planning. Use --auto to skip interactive questions (Claude picks recommended defaults). Use --chain for interactive discuss followed by automatic plan+execute. Use --power for bulk question generation into a file-based UI (answer at your own pace).

SKILL.md

3.1 KB, as published. Nobody here has run it

<objective> 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 </objective>

<execution_context> @$HOME/.claude/cds-workflow/workflows/discuss-phase.md @$HOME/.claude/cds-workflow/workflows/discuss-phase-assumptions.md @$HOME/.claude/cds-workflow/workflows/discuss-phase-power.md @$HOME/.claude/cds-workflow/templates/context.md </execution_context>

<runtime_note> Copilot (VS Code): Use vscode_askquestions wherever this workflow calls AskUserQuestion. They are equivalent — vscode_askquestions is the VS Code Copilot implementation of the same interactive question API. </runtime_note>

<context> Phase number: $ARGUMENTS (required)

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

<process> **Mode routing:** ```bash DISCUSS_MODE=$(node "$HOME/.claude/cds-workflow/bin/gsd-tools.cjs" config-get workflow.discuss_mode 2>/dev/null || echo "discuss") ```

If DISCUSS_MODE is "assumptions": Read and execute @$HOME/.claude/cds-workflow/workflows/discuss-phase-assumptions.md end-to-end.

If DISCUSS_MODE is "discuss" (or unset, or any other value): Read and execute @$HOME/.claude/cds-workflow/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>

  • 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 </success_criteria>

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.