Use when managing multiple projects simultaneously, tracking project states, syncing with GitHub Projects, or coordinating cross-project dependencies. Trigger with multi-project coordination requests.
Use when managing multiple projects simultaneously, tracking project states, syncing with GitHub Projects, or coordinating cross-project dependencies. Trigger with multi-project coordination requests.
user-invocable
false
license
Apache-2.0
compatibility
Requires access to project registry, GitHub API via gh CLI, and understanding of project lifecycle and inter-project relationships. Requires AI Maestro installed.
metadata
{"author":"Emasoft","version":"1.0.0"}
context
fork
agent
ecos-main
workflow-instruction
support
procedure
support-skill
Emasoft Chief of Staff - Multi-Project Management Skill
Overview
Multi-project management enables the Chief of Staff to oversee and coordinate work across multiple codebases, repositories, and project contexts simultaneously. This skill teaches you how to maintain a project registry, track project states, synchronize with GitHub Projects, and manage cross-project dependencies.
Prerequisites
Before using this skill, ensure:
Multiple projects exist in workspace
AI Maestro messaging is available
Project registries are accessible
Instructions
Identify cross-project coordination need
Query affected project registries
Coordinate agents across projects
Report status to EAMA
Output
Operation
Output
Cross-project query
Aggregated status from all projects
Agent reassignment
Agent moved between projects, registries updated
Resource sharing
Resource allocation adjusted across projects
What Is Multi-Project Management?
Multi-project management is the coordination of multiple independent projects under unified oversight. It involves:
Project registry: Central tracking of all active projects
State management: Tracking each project's current status and progress
GitHub sync: Bidirectional synchronization with GitHub Projects boards
Cross-project coordination: Managing dependencies between projects
# Fetch project board state
gh project list --owner Emasoft --format json | jq '.projects[] | select(.title == "SKILL_FACTORY Development")'# Update issue status
gh project item-edit --project-id PVT_xxx --id PVTI_xxx --field-id PVTF_xxx --single-select-option-id "Done"# Sync local registry after GitHub update
python scripts/ecos_sync_github_projects.py --project skill-factory --direction pull
Example 3: Cross-Project Dependency
## Cross-Project Coordination Plan### Projects Involved1. perfect-skill-suggester (PSS)
2. claude-plugins-validation (CPV)
3. emasoft-plugins-marketplace (EPM)
### Dependency Chain
PSS depends on CPV for validation
EPM depends on PSS and CPV as submodules
### Coordination Steps1. Update CPV validation logic
2. Run CPV tests (blocking)
3. Update PSS to use new CPV
4. Run PSS tests (blocking)
5. Update EPM submodules
6. Run marketplace validation
7. Publish all three
### Checkpoints- After step 2: CPV stable
- After step 4: PSS stable
- After step 6: EPM stable
Operational Procedures
Step-by-step runbooks for executing individual multi-project management operations. Use these when performing a specific operation.
op-add-project-to-registry.md - Add Project to Registry: Register a new project in the Chief of Staff's project registry, including verifying the registry file, gathering project information, validating the GitHub repository, and initializing project labels
op-sync-github-projects.md - Sync GitHub Projects: Synchronize the project registry with the GitHub Projects board by loading project configuration, fetching project items, comparing with local state, applying sync direction, and updating timestamps
op-monitor-kanban.md - Monitor Kanban Board: Proactively monitor the GitHub Project Kanban board for external changes by polling for recent card movements, status changes, new comments, and priority changes, then notifying affected agents
op-coordinate-cross-project.md - Coordinate Cross-Project Work: Coordinate work across multiple projects with dependencies by mapping dependencies, creating cross-project issues, sequencing work execution, monitoring checkpoints, and reconciling states
When to use: During active work sessions to detect external changes to the Kanban board.
Monitoring Protocol
Poll the GitHub Project board every 5 minutes during active work:
# Check for recent card movements and status changes
gh project item-list --owner Emasoft --limit 50 --format json | jq '[.items[] | select(.updatedAt > (now - 300 | strftime("%Y-%m-%dT%H:%M:%SZ")))]'# Check for new comments on project items
gh api graphql -f query='
query($owner: String!, $number: Int!) {
user(login: $owner) {
projectV2(number: $number) {
items(first: 20, orderBy: {field: UPDATED_AT, direction: DESC}) {
nodes {
content {
... on Issue {
number
title
comments(last: 5) {
nodes {
createdAt
body
}
}
}
}
}
}
}
}
}
' -f owner="Emasoft" -f number=1
What to Monitor
Change Type
Detection Method
Response
Card moved to different column
Compare status field with cached state
Notify affected agent, update local registry
New card added
Check for items with recent createdAt
Alert EOA for task assignment
Card assigned to different agent
Compare assignees field
Notify both old and new assignees
New comment added
Check comments.nodes[].createdAt
Forward comment to assigned agent
Card priority changed
Compare priority field
Notify assigned agent of priority change
Response to External Changes
When external changes are detected:
Log the change - Record timestamp, change type, and affected items
Update local registry - Sync project registry with GitHub state
Notify affected agents - Send AI Maestro message about the change
Request acknowledgment - Ensure agents are aware of new state
Use the agent-messaging skill to notify the affected agent:
Recipient: the affected agent session name
Subject: [EXTERNAL CHANGE] GitHub Project card moved
Priority: high
Content: type external-change-notification, describing what changed (card title, old status, new status, who changed it, detection timestamp), and requesting the agent to acknowledge the change
Verify: confirm message delivery and await agent acknowledgment.
Key Takeaways
Registry is source of truth - All project info flows from registry
Sync regularly with GitHub - Keep local and remote aligned
