From emasoft-assistant-manager-agent
Use when routing GitHub operations (issues, PRs, projects, releases) to the appropriate specialist agent. Trigger with GitHub-related requests.
npx claudepluginhub emasoft/emasoft-plugins --plugin emasoft-assistant-manager-agentThis skill uses the workspace's default tool permissions.
- GitHub CLI (`gh`) must be installed and authenticated
Triages GitHub issues and PRs by classifying as merge, port-rebuild, close, or park; coordinates active work with Linear for internal execution tracking. Use for backlog control, PR triage, GitHub-Linear coordination.
Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.
Processes PDFs: extracts text/tables/images, merges/splits/rotates pages, adds watermarks, creates/fills forms, encrypts/decrypts, OCRs scans. Activates on PDF mentions or output requests.
Share bugs, ideas, or general feedback.
gh) must be installed and authenticatedCopy this checklist and track your progress:
This skill provides decision trees for routing GitHub operations to the appropriate specialist role:
EIA is the default GitHub handler. Route to EAA or EOA only when the operation has design or module context.
GitHub operation requested
│
▼
┌────────────────────────────┐
│ What type of operation? │
└──────────────┬─────────────┘
│
┌──────────┼──────────┬──────────────┐
│ │ │ │
▼ ▼ ▼ ▼
ISSUE PR KANBAN/PROJECT RELEASE
│ │ │ │
▼ ▼ ▼ ▼
[Issue [PR [Project [Release
Tree] Tree] Tree] Tree]
┌─────────────────────────────────┐
│ Issue operation requested │
└───────────────┬─────────────────┘
▼
┌─────────────────────────────────┐
│ Is this linked to a design doc? │
└───────────────┬─────────────────┘
┌───────┴───────┐
│ YES │ NO
▼ ▼
┌───────────────┐ ┌─────────────────────┐
│ What action? │ │ Is this a module │
└───────┬───────┘ │ implementation task?│
│ └──────────┬──────────┘
┌───┴───┐ ┌──────┴───────┐
│ │ │ YES │ NO
▼ ▼ ▼ ▼
CREATE UPDATE ┌──────────┐ ┌──────────┐
LINK LINK │ Route to │ │ Route to │
│ │ │ EOA │ │ EIA │
│ │ └──────────┘ └──────────┘
▼ ▼
┌──────────────┐
│ Route to EAA │
│ with design │
│ UUID │
└──────────────┘
| Scenario | Route To | Handoff Content |
|---|---|---|
| Create bug report | EIA | Issue template, reproduction steps |
| Create feature request | EIA | Issue template, requirements |
| Create issue FROM design | EAA | Design UUID, section reference |
| Link existing issue to design | EAA | Issue number, design UUID |
| Update issue labels/status | EIA | Issue number, changes |
| Close issue with verification | EIA | Issue number, verification results |
| Create module task issue | EOA | Module UUID, task details |
| Track implementation progress | EOA | Issue number, module UUID |
┌─────────────────────────────────┐
│ PR operation requested │
└───────────────┬─────────────────┘
▼
┌─────────────────────────────────┐
│ What operation type? │
└───────────────┬─────────────────┘
│
┌───────────┼───────────┬────────────┐
│ │ │ │
▼ ▼ ▼ ▼
CREATE REVIEW MERGE UPDATE
│ │ │ │
▼ ▼ ▼ ▼
┌────────┐ ┌────────┐ ┌────────┐ ┌────────┐
│ Route │ │ Route │ │ Route │ │ Route │
│ to EIA │ │ to EIA │ │ to EIA │ │ to EIA │
└────────┘ └────────┘ └────────┘ └────────┘
Note: All PR operations go to EIA. EIA may consult with EAA for design validation or EOA for implementation verification.
| Operation | Route To | Handoff Content |
|---|---|---|
| Create PR | EIA | Branch, description, linked issues |
| Review PR | EIA | PR number, review criteria |
| Request changes | EIA | PR number, requested changes |
| Approve PR | EIA | PR number, approval notes |
| Merge PR | EIA | PR number, merge strategy |
| Close PR without merge | EIA | PR number, reason |
┌─────────────────────────────────┐
│ Kanban/Project operation │
└───────────────┬─────────────────┘
▼
┌─────────────────────────────────┐
│ What operation type? │
└───────────────┬─────────────────┘
│
┌───────────┼───────────┬───────────────┐
│ │ │ │
▼ ▼ ▼ ▼
SYNC CREATE MOVE STATUS
BOARD ITEM CARD QUERY
│ │ │ │
▼ ▼ ▼ ▼
┌────────┐ ┌─────────────────────┐ ┌──────────┐
│ Route │ │ Is item a design │ │ Handle │
│ to EIA │ │ or module? │ │ locally │
└────────┘ └──────────┬──────────┘ │ (EAMA) │
│ └──────────┘
┌───────┴───────┐
│ DESIGN │ MODULE
▼ ▼
┌──────────┐ ┌──────────┐
│ Route to │ │ Route to │
│ EAA │ │ EOA │
└──────────┘ └──────────┘
| Operation | Route To | Handoff Content |
|---|---|---|
| Sync board with GitHub | EIA | Project ID, sync scope |
| Create design card | EAA | Design UUID, card details |
| Create module card | EOA | Module UUID, card details |
| Move card (non-specific) | EIA | Card ID, target column |
| Move design card | EAA | Card ID, design context |
| Move module card | EOA | Card ID, module context |
| Query board status | EAMA (local) | Project ID |
| Archive completed items | EIA | Project ID, archive criteria |
┌─────────────────────────────────┐
│ Release operation requested │
└───────────────┬─────────────────┘
▼
┌─────────────────────────────────┐
│ All operations go to EIA │
│ (Integrator owns releases) │
└───────────────┬─────────────────┘
│
▼
┌──────────┐
│ Route to │
│ EIA │
└──────────┘
| Operation | Route To | Handoff Content |
|---|---|---|
| Create release | EIA | Version, changelog, assets |
| Draft release notes | EIA | Version, commit range |
| Tag version | EIA | Tag name, commit SHA |
| Publish release | EIA | Release ID, publish settings |
| Update release | EIA | Release ID, changes |
## GitHub Operation Handoff
**Operation Type**: [issue|pr|kanban|release]
**Action**: [create|update|close|merge|sync|etc.]
**Target**: [repo, issue number, PR number, project ID]
### Details
- Specific operation parameters
- Any linked references
### Expected Outcome
- What success looks like
- Verification criteria
## Design-GitHub Link Handoff
**Design UUID**: [uuid]
**Design Path**: [path to design doc]
**GitHub Target**: [issue/card number or ID]
### Link Context
- Why this link exists
- What the GitHub item represents in the design
### Expected Outcome
- Design doc updated with GitHub reference
- GitHub item updated with design reference
## Module-GitHub Handoff
**Module UUID**: [uuid]
**Design Reference**: [design UUID]
**GitHub Target**: [issue/card number or ID]
### Implementation Context
- Module's role in overall implementation
- Dependencies on other modules
### Task Details
- Specific implementation task
- Acceptance criteria
When creating GitHub items linked to designs/modules, include UUID reference:
In Issue Body:
<!-- EAMA-LINK: design-uuid=abc123 -->
<!-- EAMA-LINK: module-uuid=def456 -->
In PR Description:
## Related Design
Design UUID: `abc123` (path: `design/feature-x/DESIGN.md`)
## Implementing Modules
- Module UUID: `def456` (component-a)
- Module UUID: `ghi789` (component-b)
In Kanban Card Notes:
DESIGN: abc123
MODULE: def456
EAMA can find GitHub items by UUID using:
gh issue list --search "EAMA-LINK: design-uuid=abc123"
gh pr list --search "Design UUID: abc123"
If operation could go to multiple agents:
If handoff lacks required information:
If target agent is not responding:
After routing a GitHub operation, EAMA should produce:
| Output Element | Content |
|---|---|
| Routing Decision | Which agent (EIA/EAA/EOA/EAMA) received the operation |
| Operation Type | Issue/PR/Kanban/Release |
| Handoff Status | Sent/Queued/Failed |
| Tracking Reference | UUID or GitHub item number for follow-up |
Format:
[ROUTED] GitHub {operation_type} → {target_agent}
Handoff: {status}
Reference: {tracking_id}
# User request
"Create an issue for the login timeout bug"
# EAMA decision process
1. Operation type: ISSUE
2. Is linked to design doc? NO
3. Is module implementation task? NO
4. Route to: EIA
# Handoff content
## GitHub Operation Handoff
**Operation Type**: issue
**Action**: create
**Target**: main repo
### Details
- Title: Login timeout bug
- Labels: bug, high-priority
- Body: Users experiencing timeout after 30 seconds
### Expected Outcome
- Issue created with appropriate labels
- Issue number returned
# User request
"Create a kanban card for the authentication design"
# EAMA decision process
1. Operation type: KANBAN
2. Is item design or module? DESIGN
3. Route to: EAA
# Handoff includes design UUID for linking
For proactive kanban monitoring procedures, see proactive-kanban-monitoring.md: