vaultspec-projectmanagerlisted

# Project coordination Aggregate context into an actionable sequence for a developer managing several in-flight features or an epic and its tracker. Activate for a request to coordinate that work. GitHub usage, multiple branches, and worktrees alone do not justify loading this skill. Handle bounded repository questions and single-PR work directly. Coordination can be entirely local. Use tracker access when remote state matters; missing access leaves those facts unknown without blocking a local workday plan. ## Method 1. **Set the outcome.** Establish the horizon, workstreams, developer availability, priorities, and existing authority. Reuse supplied context; ask only for a missing constraint that would materially change the sequence. 1. **Collect relevant state.** Reuse supplied observations. When acquisition is needed, run `vaultspec-core project context "<objective>" --json`; add `--repo OWNER/REPO` for GitHub issues and PRs. It returns bounded Git state, attention signals, coverage, and unknowns. Fetch board, milestone, dependency and vault-plan context only as needed. Follow pagination when claiming complete coverage; otherwise state the window. Retain identifiers and observation times; distinguish facts from inferred relationships. 1. **Choose a sequence.** Connect features, issues, PRs, plans, and worktrees where evidence supports the relationship. Identify blockers, competing ownership, stale assignments, and local/remote discrepancies