Claude Code Skills · page 136

Start a new milestone cycle — update PROJECT.md and route to requirements

Initialize a new project with deep context gathering and PROJECT.md

Create an isolated workspace with repo copies and independent .planning/

Automatically advance to the next logical step in the MindForge workflow

Zero-friction idea capture. Append, list, or promote notes to todos.

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

Create context handoff when pausing work mid-phase

Create phases to close all gaps identified by milestone audit

Create detailed phase plan (PLAN.md) with verification loop

Use when you have a spec or requirements for a multi-step task, before touching code

Capture a forward-looking idea with trigger conditions — surfaces automatically at the right milestone

Create a clean PR branch by filtering out .planning/ commits — ready for code review

Generate developer behavioral profile and create Claude-discoverable artifacts

Check project progress, show context, and route to next action (execute or plan)

Execute a quick task with MindForge guarantees (atomic commits, state tracking) but skip optional agents

Reapply local modifications after a MindForge update

Remove a future phase from roadmap and renumber subsequent phases

Remove a MindForge workspace and clean up worktrees

Research how to implement a phase (standalone - usually use /mindforge-plan-phase instead)

Resume work from previous session with full context restoration

Review and promote backlog items to active milestone

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Request cross-AI peer review of phase plans from external AI CLIs

Generate a session report with token usage estimates, work summary, and outcomes

Switch model profile for MindForge agents (quality/balanced/budget/inherit)

Configure MindForge workflow toggles and model profile

Create PR, run review, and prepare for merge after verification passes

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

Use when creating new skills, editing existing skills, or verifying skills work before deployment

Display project statistics — phases, plans, requirements, git metrics, and timeline

Use when executing implementation plans with independent tasks in the current session

Design systems with appropriate complexity - no more, no less. Use when the user asks to architect applications, design system boundaries, plan service decomposition, evaluate monolith vs microservices, make scaling decisions, or review structural trade-offs. Applies to new system design, refactoring, and migration planning.

Strict TDD workflow (Red-Green-Refactor).

Use when implementing any feature or bugfix, before writing implementation code

Manage persistent context threads for cross-session work

Generate UI design contract (UI-SPEC.md) for frontend phases

Retroactive 6-pillar visual audit of implemented frontend code

Update MindForge to latest version with changelog display

Retroactively audit and fill Nyquist validation gaps for a completed phase

Validate built features through conversational UAT

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

Manage parallel workstreams — list, create, switch, status, progress, complete, and resume

Publish a skill to the npm registry (or private registry).