What problem does it solve? Developers on the mj-agent project must follow a strict bare-repo plus worktree-per-branch convention with five branch types, and manually constructing the correct worktree-add commands and choosing the right branch type is error-prone. ## Core Features & Use Cases - Branch Type Decision: Maps task nature (new feature, bug fix, docs-only, infrastructure maintenance, production hotfix) to the correct branch type among feature, bugfix, documentation, maintain, and hotfix. - Worktree Command Generation: Produces ready-to-run git worktree add commands targeting the correct base branch (develop for most types, main for hotfix) in the bare-repo layout. - Health Check & Recovery: Diagnoses broken worktrees via git rev-parse and repairs config.worktree drift with a PowerShell fix. - Use Case: A developer says "start a feature for the flow intake skill" and receives the exact command git worktree add ../feature/63-add-flow-intake-skill -b feature/63-add-flow-intake-skill develop executed from the develop worktree. ## Quick Start Ask the assistant to create a new branch for your mj-agent task, describing whether it is a feature, bugfix, documentation, maintenance, or hotfix, and it will output the exact worktree-add command to run.
