From emasoft-assistant-manager-agent
Use when managing GitHub issue labels for user requests, setting priorities, or reporting status to users. Covers priority and status label taxonomy. Trigger with `/eama-label-taxonomy`.
npx claudepluginhub emasoft/emasoft-plugins --plugin emasoft-assistant-manager-agentThis skill uses the workspace's default tool permissions.
This skill provides the label taxonomy relevant to the Assistant Manager Agent (EAMA) role. Each role plugin has its own label-taxonomy skill covering the labels that role manages.
Manages GitHub issue labels via gh CLI using AMOA taxonomy. Applies categories like assign:*, status:*, priority:* ensuring cardinality rules. Triggers on label queries or assignments.
Triages GitHub issues assigned to you: fetches via GH CLI with cc-triage-scope label, builds dependency graph, categorizes resolved issues, and applies labels (cc-create-issue, cc-exec-issue, cc-update-issue).
Triages project issues via label state machine with bug/enhancement categories and states like needs-triage, needs-info, ready-for-agent. Use for reviewing bugs, features, or workflows.
Share bugs, ideas, or general feedback.
This skill provides the label taxonomy relevant to the Assistant Manager Agent (EAMA) role. Each role plugin has its own label-taxonomy skill covering the labels that role manages.
gh) commandFollow these steps to manage labels as EAMA:
status:backlog, priority:*, type:*)status:blocked)Checklist for label management:
Copy this checklist and track your progress:
backlogstatus:human-review is setpriority:*)EAMA has authority to set and change priorities based on user input.
| Label | Description | When EAMA Sets It |
|---|---|---|
priority:critical | Must fix immediately | User reports production issue |
priority:high | High priority | User emphasizes importance |
priority:normal | Standard priority | Default for new issues |
priority:low | Nice to have | User indicates low urgency |
EAMA Priority Responsibilities:
The full workflow uses these 8 status columns:
| # | Column Code | Display Name | Label | Description |
|---|---|---|---|---|
| 1 | backlog | Backlog | status:backlog | Entry point for new tasks |
| 2 | todo | Todo | status:todo | Ready to start |
| 3 | in-progress | In Progress | status:in-progress | Active work |
| 4 | ai-review | AI Review | status:ai-review | Integrator agent reviews ALL tasks |
| 5 | human-review | Human Review | status:human-review | User reviews BIG tasks only (via EAMA) |
| 6 | merge-release | Merge/Release | status:merge-release | Ready to merge |
| 7 | done | Done | status:done | Completed |
| 8 | blocked | Blocked | status:blocked | Blocked at any stage |
Task Routing Rules:
| Label | When EAMA Sets It |
|---|---|
status:backlog | When creating new issue from user request |
status:human-review | When EIA escalates a significant task for user review |
status:blocked | When user requests pause or issue cannot proceed |
status:*)EAMA reports status to user:
status:backlog - "Your request has been logged"status:todo - "Your request is queued and ready to start"status:in-progress - "Work has started on your request"status:ai-review - "The AI integrator is reviewing the work"status:human-review - "This needs your review and testing"status:merge-release - "Code is approved and ready to merge"status:blocked - "There's a blocker, may need your input"status:done - "Your request is complete"assign:*)EAMA explains assignments to user:
assign:implementer-* - "An AI agent is working on this"assign:human - "This needs human attention"assign:orchestrator - "The orchestrator is handling this"# Create issue with initial labels
gh issue create \
--title "$USER_REQUEST_TITLE" \
--body "$USER_REQUEST_BODY" \
--label "status:backlog" \
--label "priority:$PRIORITY" \
--label "type:$TYPE"
# Update priority
gh issue edit $ISSUE_NUMBER --remove-label "priority:normal" --add-label "priority:high"
# Mark blocked
gh issue edit $ISSUE_NUMBER --remove-label "status:in-progress" --add-label "status:blocked"
# Present the task to the user for review (escalated from AI Review)
gh issue view $ISSUE_NUMBER --json title,body,labels
# After user approves:
gh issue edit $ISSUE_NUMBER --remove-label "status:human-review" --add-label "status:merge-release"
# After user requests changes:
gh issue edit $ISSUE_NUMBER --remove-label "status:human-review" --add-label "status:in-progress"
# Get all active issues for user
gh issue list --label "status:in-progress" --json number,title,labels
# Get issues in AI review
gh issue list --label "status:ai-review" --json number,title,labels
# Get issues awaiting human review
gh issue list --label "status:human-review" --json number,title,labels
# Get blocked issues needing attention
gh issue list --label "status:blocked" --json number,title,labels
# Get completed issues
gh issue list --label "status:done" --state closed --json number,title
When user asks "What's happening with my request?":
**Issue #42: Add user authentication**
- **Status**: In Progress (`status:in-progress`)
- **Priority**: High (`priority:high`)
- **Assigned to**: Implementation Agent 1 (`assign:implementer-1`)
- **Type**: New Feature (`type:feature`)
The implementation agent is actively working on this task.
| User Says | Labels to Apply |
|---|---|
| "This is urgent!" | priority:critical |
| "When you get a chance..." | priority:low |
| "Something is broken" | type:bug, priority:high |
| "Can you add..." | type:feature |
| "Put this on hold" | status:blocked |
| "Resume this" | Remove status:blocked, add status:todo |
| Action | Labels Involved |
|---|---|
| Create issue | status:backlog, priority:*, type:* |
| Change priority | Update priority:* |
| Pause work | Add status:blocked |
| Resume work | Remove status:blocked, add status:todo |
| Facilitate human review | Manage status:human-review transitions |
| Report to user | Read all labels for status |
assign:* - Set by EOA/ECOSreview:* - Managed by EIAeffort:* - Set by EOA during triagecomponent:* - Set by EOA/EAAEAMA can approve:
EAMA must approve:
priority:criticalassign:human| Output Type | Format | When Generated |
|---|---|---|
| Issue creation | GitHub issue URL with labels | When user creates new request |
| Label update confirmation | "Priority updated to high" | When labels modified |
| Status report | Markdown table of issues and labels | When user requests status |
| Label explanation | Plain text translation of label meaning | When user asks "what's happening?" |
| Error | Cause | Resolution |
|---|---|---|
| Label not found | Typo or label doesn't exist in repo | Create label or fix typo |
| Permission denied | Insufficient GitHub permissions | Request repo access from user |
| Issue not found | Invalid issue number | Verify issue number with user |
| Conflicting labels | Multiple priority labels applied | Remove old label before adding new |
| API rate limit | Too many GitHub API calls | Wait and retry, batch operations |
User request: "The login page is broken, fix it urgently!"
EAMA actions:
gh issue create \
--title "Login page broken" \
--body "User reported urgent login page issue" \
--label "type:bug" \
--label "priority:critical" \
--label "status:backlog"
User response: "Created issue #123 with critical priority. The orchestrator will triage this shortly."
User request: "What's the status of my authentication work?"
EAMA actions:
gh issue list --label "component:auth" --json number,title,labels
User response:
**Authentication Issues**:
- **#42**: Add OAuth support
- Status: In Progress (`status:in-progress`)
- Priority: High (`priority:high`)
- Assigned to: Implementation Agent 1
- **#45**: Fix password reset
- Status: Blocked (`status:blocked`)
- Priority: Normal (`priority:normal`)
- Blocker: Waiting for email service setup
User request: "Actually, make that password reset high priority too."
EAMA actions:
gh issue edit 45 --remove-label "priority:normal" --add-label "priority:high"
User response: "Priority updated to high for issue #45."