mindforge-new-workspace
mindforge-new-workspace creates an isolated development environment by setting up git worktrees or clones of specified repositories alongside an independent `.planning/` directory for separate MindForge sessions. Use this skill when orchestrating work across multiple repositories in parallel or when establishing feature-branch-specific workspaces with isolated planning state, each with its own workspace manifest and configuration.
git clone --depth 1 https://github.com/sairam0424/MindForge /tmp/mindforge-new-workspace && cp -r /tmp/mindforge-new-workspace/.agent/skills/mindforge-new-workspace ~/.claude/skills/mindforge-new-workspaceSKILL.md
<context> **Flags:** - `--name` (required) — Workspace name - `--repos` — Comma-separated repo paths or names. If omitted, interactive selection from child git repos in cwd - `--path` — Target directory. Defaults to `~/mindforge-workspaces/<name>` - `--strategy` — `worktree` (default, lightweight) or `clone` (fully independent) - `--branch` — Branch to checkout. Defaults to `workspace/<name>` - `--auto` — Skip interactive questions, use defaults </context> <objective> Create a physical workspace directory containing copies of specified git repos (as worktrees or clones) with an independent `.planning/` directory for isolated MindForge sessions. **Use cases:** - Multi-repo orchestration: work on a subset of repos in parallel with isolated MindForge state - Feature branch isolation: create a worktree of the current repo with its own `.planning/` **Creates:** - `<path>/WORKSPACE.md` — workspace manifest - `<path>/.planning/` — independent planning directory - `<path>/<repo>/` — git worktree or clone for each specified repo **After this command:** `cd` into the workspace and run `/mindforge-new-project` to initialize MindForge. </objective> <execution_context> @.agent/workflows/mindforge-new-workspace.md @.agent/references/ui-brand.md </execution_context> <process> Execute the new-workspace workflow from @.agent/workflows/mindforge-new-workspace.md end-to-end. Preserve all workflow gates (validation, approvals, commits, 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