mindforge-quick
Mindforge-quick executes small, self-contained tasks with guaranteed atomic commits and STATE.md tracking while bypassing research, discussion, and verification phases by default. Use this when task requirements are clear and execution is straightforward; add optional flags like --discuss, --research, or --full when ambiguity, uncertainty about approach, or quality verification becomes necessary.
git clone --depth 1 https://github.com/sairam0424/MindForge /tmp/mindforge-quick && cp -r /tmp/mindforge-quick/.agent/skills/mindforge-quick ~/.claude/skills/mindforge-quickSKILL.md
<objective> Execute small, ad-hoc tasks with MindForge guarantees (atomic commits, STATE.md tracking). Quick mode is the same system with a shorter path: - Spawns mindforge-planner (quick mode) + mindforge-executor(s) - Quick tasks live in `.planning/quick/` separate from planned phases - Updates STATE.md "Quick Tasks Completed" table (NOT ROADMAP.md) **Default:** Skips research, discussion, plan-checker, verifier. Use when you know exactly what to do. **`--discuss` flag:** Lightweight discussion phase before planning. Surfaces assumptions, clarifies gray areas, captures decisions in CONTEXT.md. Use when the task has ambiguity worth resolving upfront. **`--full` flag:** Enables plan-checking (max 2 iterations) and post-execution verification. Use when you want quality guarantees without full milestone ceremony. **`--research` flag:** Spawns a focused research agent before planning. Investigates implementation approaches, library options, and pitfalls for the task. Use when you're unsure of the best approach. Flags are composable: `--discuss --research --full` gives discussion + research + plan-checking + verification. </objective> <execution_context> @.agent/workflows/mindforge-quick.md </execution_context> <context> $ARGUMENTS Context files are resolved inside the workflow (`init quick`) and delegated via `<files_to_read>` blocks. </context> <process> Execute the quick workflow from @.agent/workflows/mindforge-quick.md end-to-end. Preserve all workflow gates (validation, task description, planning, execution, state updates, commits). </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