Skill0 repo starsupdated yesterday

mindforge-discuss-phase

mindforge-discuss-phase is a Claude Code skill that gathers implementation decisions for a specific project phase by loading prior context, identifying unresolved design questions, and conducting targeted discussions with the user until decisions are clear. Use this before research and planning phases to create a CONTEXT.md file that prevents downstream agents from re-asking already-decided questions and ensures they have concrete direction for investigation and execution.

View source Repository: MindForge

Install in Claude Code

Copy

git clone --depth 1 https://github.com/sairam0424/MindForge /tmp/mindforge-discuss-phase && cp -r /tmp/mindforge-discuss-phase/.agent/skills/mindforge-discuss-phase ~/.claude/skills/mindforge-discuss-phase

Then start a new Claude Code session; the skill loads automatically.

Definition

SKILL.md

<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>
@.agent/workflows/mindforge-discuss-phase.md
@.agent/workflows/mindforge-discuss-phase-assumptions.md
@.agent/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>

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

If `DISCUSS_MODE` is `"assumptions"`: Read and execute @.agent/workflows/mindforge-discuss-phase-assumptions.md end-to-end.

If `DISCUSS_MODE` is `"discuss"` (or unset, or any other value): Read and execute @.agent/workflows/mindforge-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>