phased-development

To coordinate multiple Claude Code sessions across project phases, this Skill detects the current branch tier and loads the matching orchestration role. It enforces branch-to-role consistency and provides peer activity summaries for synchronized multi-session work.

Branch tier routing in phased software development identifies whether a session is on planning, phase, epic, sprint, or hotfix branches. It then selects the correct orchestration role to ensure Claude Code aligns with the repository's specific phase conventions.

Yes, you need a .claude/orchestration.yaml file to use branch pattern matching with Claude Code. This configuration file is required for the Skill to verify roles, check plugin versions, and safely load the proper downstream skill.

Set up Claude Code for multi-phase planning and sprint implementation by applying phased-development branch conventions to your repository. The Skill inspects the repository, determines the branch tier, and loads the appropriate role skill for epic coordination and sprint work.

Yes, Claude Code works with GitHub worktrees for hotfix handling and epic coordination. The Skill routes sessions to the correct orchestration role by matching branch patterns, ensuring hotfix branches and epic branches load their respective downstream skills.

If Claude Code loads the wrong role for your git branch, the branch pattern matching may be failing due to missing .claude/orchestration.yaml configuration or unverified branch tier conventions. The Skill requires this file to enforce branch-to-role consistency safely.