Skip to content
Back to skills

Multi Phase Sync

ASecurity

Syncs the main plan PR with current progress from phase PRs. Invoked when the user wants to sync the main plan, update the main plan PR, update the roadmap, or runs /aido:multi-phase-sync.

  • 6 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 6, 2026
developmentgit

Works with

  • cli

Security analysis

A100/100

Scanned November 11, 2026

npx -y skills add joebew42/aido --skill multi-phase-sync --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Multi Phase Sync?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Multi Phase Sync
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/joebew42-multi-phase-sync/badge)](https://www.skillsdirectory.com/skills/joebew42-multi-phase-sync)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
description: Syncs the main plan PR with current progress from phase PRs. Invoked when the user wants to sync the main plan, update the main plan PR, update the roadmap, or runs /aido:multi-phase-sync.
disable-model-invocation: false
---

# Sync Multi-Phase Plan

**In Copilot CLI only:** before anything else, read `guidelines/copilot-cli.md` in the plugin root, two folders above this skill's base directory, and follow it. Read every guideline this skill names whole, with `view`, one file per call.

Update the main plan PR from the state of each phase PR.

Load `${CLAUDE_PLUGIN_ROOT}/guidelines/git-workflow.md`.

Load `${CLAUDE_PLUGIN_ROOT}/guidelines/language.md` and follow it in everything you write for a person.

## Process

1. switch to the feature's main plan branch
2. rebase it onto `origin/<default-branch>`:
   - run `git fetch origin`
   - run `git rebase origin/<default-branch>`
3. check the state of every phase PR:
   - read the main plan PR's description with `gh pr view --json body`
   - take every PR number the roadmap already names, such as `(#41)`
   - fetch each one's latest state directly:
     `gh pr view <NUMBER> --json number,title,state,headRefName,mergedAt`
   - find no PR by searching, as "Using GitHub CLI" in `git-workflow.md` says
4. from those states, update:
   - the main plan PR's description, with the roadmap's current state
   - the specification, if the finished phases taught something it needs
5. delete the local branch of each merged phase PR:
   - get its name with `gh pr view <PR_NUMBER> --json headRefName`
   - delete it with `git branch -D <branch_name>`. Skip it if it doesn't exist locally
6. when every phase is merged and the specification is fully built:
   - close the main plan PR with `gh pr close <PR_NUMBER> --comment "All phases completed and merged."`
   - delete the local main plan branch with `git branch -D <main_plan_branch>`
7. when phases remain, ask the user whether the specification needs changes or clarifications
8. end as "Ending a Skill" in `${CLAUDE_PLUGIN_ROOT}/guidelines/language.md` describes.

## Templates

When updating the roadmap, follow the format rules in `${CLAUDE_PLUGIN_ROOT}/guidelines/pr-roadmap.md`.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in development →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.