orchestrating-as-primary

Coordinate multi-phase software projects across planning, worktrees, issues, and pull requests.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/tuvens/phased-development --skill orchestrating-as-primary
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orchestrating-as-primary
Source: https://github.com/tuvens/phased-development/tree/main/skills/orchestrating-as-primary
Command: npx skills add https://github.com/tuvens/phased-development --skill orchestrating-as-primary

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill keeps long-running software projects coordinated across phases, worktrees, issues, pull requests, and cross-session signals so the planning branch stays accurate and nothing gets lost between Claude Code sessions.

Core Features & Use Cases

  • Phase orchestration: Guides the primary engineering role through phase starts, phase completion, issue intake, reassignment, PR review, hotfix dispatch, and deferred cleanup.
  • Roadmap and worktree governance: Maintains the phase roadmap, audits active worktrees, and enforces cleanup rules so the roadmap matches the filesystem and GitHub state.
  • Cross-session coordination: Reads status-board updates and signal files, applies decisions safely, and keeps leadership and phase leads aligned over long project timelines.
  • Use case: A team running a months-long Claude Code project can use this Skill to keep epics, sprints, labels, and merge gates synchronized while avoiding duplicate work or orphaned branches.

Quick Start

Use the orchestrating-as-primary skill to act as the VP of Engineering for this phased project and keep the roadmap, worktrees, issues, and pull requests synchronized.

Frequently Asked Questions about orchestrating-as-primary

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I coordinate multi-phase software projects across Claude Code sessions?

Multi-phase software project orchestration coordinates planning, phase transitions, issue triage, and PR reviews across Claude Code sessions by using worktrees, roadmap tracking, and status-board signals to keep long-running projects synchronized.

How do I keep my GitHub roadmap in sync with active worktrees during long-running development?

GitHub roadmap and worktree governance audits active worktrees and enforces cleanup rules, ensuring the phase roadmap accurately matches the filesystem and GitHub state while preventing orphaned branches and duplicate work.

What is the best way to manage phase transitions and hotfix dispatch in GitHub-based development?

Phase orchestration guides the primary engineering role through phase starts, phase completion, issue intake, reassignment, PR review, hotfix dispatch, and deferred cleanup to keep GitHub-based development synchronized.

Can I use Claude Code for cross-session coordination with GitHub issues and pull requests?

Yes, Claude Code cross-session coordination reads status-board updates and signal files, applying decisions safely to keep leadership and phase leads aligned over long project timelines with GitHub issues and PRs.

When do I need worktree audits and branch cleanup for multi-phase project orchestration?

Worktree audits and branch cleanup are needed when maintaining a phase roadmap across long-running Claude Code projects to enforce cleanup rules, avoid orphaned branches, and ensure the filesystem matches the roadmap.