solo-parallel-dev

What problem does it solve?

Solo developers often struggle with context switching overhead, self-induced merge conflicts from editing shared files across branches, and abandoned half-finished work when juggling multiple feature, fix, or documentation branches without a structured workflow.

Core Features & Use Cases

• Worktree-based branch isolation: Use git worktree to create separate physical directories for each active branch, eliminating the need to stash changes or rely on memory for context.
• Branch status kanban: Maintain a simple markdown kanban to track the status, progress, blockers, and next steps for each active branch to avoid forgetting work context.
• Conflict prevention rules: Follow clear guidelines for modifying shared repository files (like README.md) across branches to avoid self-merge conflicts.
• Context recovery protocol: Use a standardized 3-step process to quickly resume work on a branch after days of inactivity without losing track of prior decisions.
• Merge ordering strategy: Sort branch merges by size to minimize conflict resolution effort and keep the main branch stable. Use case: A solo dev working on a backend feature upgrade, a new AI safety skill, and a small README typo fix at the same time can use this workflow to complete all three tasks without mixing up changes or losing track of progress.

Quick Start

Use the solo-parallel-dev skill to set up a parallel development workflow for my three current feature branches and create a branch status kanban to track their progress.