mindforge-plan-phase
The mindforge-plan-phase skill generates detailed PLAN.md files for roadmap phases by orchestrating research, planning, and verification cycles. Use it to create executable phase prompts with optional domain research, cross-AI review integration, adversarial decision synthesis, and gap closure modes, supporting both interactive and remote environments.
git clone --depth 1 https://github.com/sairam0424/MindForge /tmp/mindforge-plan-phase && cp -r /tmp/mindforge-plan-phase/.agent/skills/mindforge-plan-phase ~/.claude/skills/mindforge-plan-phaseSKILL.md
<objective> Create executable phase prompts (PLAN.md files) for a roadmap phase with integrated research and verification. **Default flow:** Research (if needed) → Plan → Verify → Done **Orchestrator role:** Parse arguments, validate phase, research domain (unless skipped), spawn mindforge-planner, verify with mindforge-plan-checker, iterate until pass or max iterations, present results. </objective> <execution_context> @.agent/workflows/mindforge-plan-phase.md @.agent/references/ui-brand.md </execution_context> <context> Phase number: $ARGUMENTS (optional — auto-detects next unplanned phase if omitted) **Flags:** - `--research` — Force re-research even if RESEARCH.md exists - `--skip-research` — Skip research, go straight to planning - `--gaps` — Gap closure mode (reads VERIFICATION.md, skips research) - `--skip-verify` — Skip verification loop - `--prd <file>` — Use a PRD/acceptance criteria file instead of discuss-phase. Parses requirements into CONTEXT.md automatically. Skips discuss-phase entirely. - `--reviews` — Replan incorporating cross-AI review feedback from REVIEWS.md (produced by `/mindforge-review`) - `--ads` — Use Adversarial Decision Synthesis (Architect vs Auditor) for high-fidelity planning - `--text` — Use plain-text numbered lists instead of TUI menus (required for `/rc` remote sessions) Normalize phase input in step 2 before any directory lookups. </context> <process> Execute the plan-phase workflow from @.agent/workflows/mindforge-plan-phase.md end-to-end. Preserve all workflow gates (validation, research, planning, verification loop, routing). </process>
Publish a skill to the npm registry (or private registry).
Add an idea to the backlog parking lot (999.x numbering)
Add phase to end of current milestone in roadmap
Generate tests for a completed phase based on UAT criteria and implementation
Capture idea or task as todo from current conversation context
Audit milestone completion against original intent before archiving
Cross-phase audit of all outstanding UAT and verification items
Run all remaining phases autonomously — discuss→plan→execute per phase