メニュー
Use when managing GitHub labels for the Architect Agent: component, effort, type, and priority labels. Trigger with label management or taxonomy request. Loaded by ai-maestro-architect-agent-main-agent
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when decomposing systems into modules with clear boundaries. Trigger with modularization or module boundary request. Loaded by ai-maestro-architect-agent-main-agent
Use when designing architectures, identifying risks, creating roadmaps, or breaking work into tasks. Trigger with planning or architecture design request. Loaded by ai-maestro-architect-agent-main-agent
Use when managing requirements, initializing plans, or approving transitions. Trigger with requirements analysis or plan initialization request. Loaded by ai-maestro-architect-agent-main-agent
Use when recording stack choices, constraints, or managing handoffs. Trigger with session memory ops request. Loaded by ai-maestro-architect-agent-main-agent
Use when persisting decisions, patterns, and constraints across sessions. Trigger with session memory or handoff request. Loaded by ai-maestro-architect-agent-main-agent
Use when managing design document states or lifecycle transitions. Trigger with design lifecycle or state transition request. Loaded by ai-maestro-architect-agent-main-agent
| name | amaa-label-taxonomy |
| description | Use when managing GitHub labels for the Architect Agent: component, effort, type, and priority labels. Trigger with label management or taxonomy request. Loaded by ai-maestro-architect-agent-main-agent |
| context | fork |
| agent | ai-maestro-architect-agent-main-agent |
| user-invocable | false |
Provides the label taxonomy for the Architect Agent (AMAA) role. AMAA recommends component:* labels, validates effort:* estimates, and may suggest type:* changes based on architecture analysis. Each role plugin has its own label-taxonomy skill.
gh) installed and authenticatedCopy this checklist and track your progress:
priority:* labels to scope design constraintseffort:* against design complexitycomponent:* labels from module breakdowntype:*, component:*, status:backlogpriority:* labels to scope design constraintseffort:* against design complexitycomponent:* labels from module breakdowntype:*, component:*, status:backlog| Document | Description |
|---|---|
| label-taxonomy-details.md | Component Labels (component:*), Kanban Columns (Canonical 5-Column System), Type Labels AMAA Clarifies, Priority Labels (priority:*) - Read by AMAA, Effort Labels (effort:*) - Validated by AMAA, Architecture-to-Labels Mapping, Architecture Breakdown |
| examples-extended.md | Extended examples with bash commands (Example 1: Adding Component Labels After Architecture Analysis, Example 2: Validating Effort Estimate, Example 3: Creating Component-Specific Sub-Issues, Example 4: Architecture Decision Record (ADR)) |
| op-add-component-labels.md | Purpose, When to Use, Prerequisites, Procedure, Example, Component Label Reference, Error Handling |
# After architecture analysis of issue #123 (API + DB changes, effort upgrade)
gh issue edit 123 --add-label "component:api" --add-label "component:database"
gh issue edit 123 --remove-label "effort:s" --add-label "effort:m"
| Error | Cause | Solution |
|---|---|---|
label not found | Label does not exist | Create via gh label create |
permission denied | No write access | Verify GitHub token scopes |
issue not found | Invalid issue number | Check with gh issue list |
| Output Type | Format |
|---|---|
| Component recommendations | Issue comment listing affected components |
| Label updates | CLI stdout confirmation |
| Sub-issue creation | New issue URL |