Use when applying or checking GitHub labels for agent assignment and status tracking. GitHub label taxonomy reference for the Chief of Staff Agent. Trigger with `/ecos-label-taxonomy`.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.
Use when applying or checking GitHub labels for agent assignment and status tracking. GitHub label taxonomy reference for the Chief of Staff Agent. Trigger with `/ecos-label-taxonomy`.
context
fork
user-invocable
false
license
Apache-2.0
compatibility
Requires AI Maestro installed.
version
1.0.0
metadata
{"author":"Emasoft"}
workflow-instruction
support
procedure
support-skill
ECOS Label Taxonomy
Overview
This skill provides the label taxonomy relevant to the Chief of Staff Agent (ECOS) role. Each role plugin has its own label-taxonomy skill covering the labels that role manages.
Prerequisites
GitHub repository with label support
Understanding of agent role prefixes (ecos-, eoa-, eia-, eaa-, eama-)
Read AGENT_OPERATIONS.md in docs/ folder for session naming
GitHub CLI (gh) installed and authenticated
Access to team registry at .emasoft/team-registry.json
Instructions
Identify the label category needed (assign, status, priority)
Check if label exists on the issue/PR
Apply or modify label using gh CLI or GitHub API
Verify label was applied correctly
Update team registry if assignment labels changed
Checklist
Copy this checklist and track your progress:
Identify label category (assign/status/priority)
Check existing labels on issue with gh issue view <number>
Remove conflicting labels if needed
Apply new label via gh issue edit --add-label
Verify label appears correctly
Update .emasoft/team-registry.json if agent assignment changed
status:in-progress - Track for timeout/health monitoring
status:ai-review - Route to EIA if not already
status:human-review - Escalated for user review via EAMA
status:merge-release - Ready to merge/release
ECOS Label Commands
When Agent Spawned
# Assign new agent to issue
gh issue edit $ISSUE_NUMBER --add-label "assign:$NEW_AGENT_NAME"
gh issue edit $ISSUE_NUMBER --remove-label "status:backlog" --add-label "status:todo"
When Agent Terminated
# Clear assignment from all agent's issues
AGENT_ISSUES=$(gh issue list --label "assign:$AGENT_NAME" --json number --jq '.[].number')
for ISSUE in$AGENT_ISSUES; do
gh issue edit $ISSUE --remove-label "assign:$AGENT_NAME" --add-label "status:backlog"done
# Reassign to human
gh issue edit $ISSUE_NUMBER --remove-label "assign:$AGENT_NAME" --add-label "assign:human"
Agent Registry and Labels
ECOS maintains the team registry at .emasoft/team-registry.json. Labels should be synchronized:
{"agents":{"implementer-1":{"session_name":"code-impl-01","status":"active","current_issues":[42,43]// Should match assign:implementer-1 labels}}}
Sync Check
# Find issues assigned to agent
LABELED=$(gh issue list --label "assign:implementer-1" --json number --jq '.[].number' | sort)
# Compare with registry
REGISTERED=$(jq -r '.agents["implementer-1"].current_issues | sort | .[]' .emasoft/team-registry.json)
# Should match
Operational Procedures
Step-by-step runbooks for executing individual label management operations. Use these when performing a specific label-related operation.
op-assign-agent-to-issue.md - Assign Agent to Issue: Assign a newly spawned or existing agent to a GitHub issue by applying the assignment label, updating status from backlog to ready, and updating the team registry
op-terminate-agent-clear-assignments.md - Terminate Agent and Clear Assignments: When an agent is being terminated, find all its assigned issues, remove assignment labels, return issues to backlog, and remove agent from team registry
op-handle-blocked-agent.md - Handle Blocked Agent: When an agent reports it's blocked on an issue, update the issue status to blocked, add a comment explaining the blocker, determine escalation level, and optionally escalate to human
op-sync-registry-with-labels.md - Sync Registry with Labels: Ensure the team registry at .emasoft/team-registry.json stays synchronized with GitHub issue assignment labels by detecting and resolving discrepancies
Quick Reference
ECOS Label Responsibilities
Action
Labels Involved
Spawn agent
Add assign:<agent>, update status:todo
Terminate agent
Remove assign:<agent>, set status:backlog
Agent blocked
Update to status:blocked
Resolve blocker
Update to status:todo or status:in-progress
Escalate to human
Add assign:human
Block work
Add status:blocked
Labels ECOS Never Sets
type:* - Set at issue creation
effort:* - Set during triage by EOA
review:* - Managed by EIA
priority:* - Set by EOA or EAMA (ECOS can suggest changes)
Resources
AGENT_OPERATIONS.md - Canonical operations reference (in docs/ folder)
