amoa-label-taxonomy

Use when applying GitHub labels. Trigger with label query or assignment requests. Loaded by ai-maestro-orchestrator-agent-main-agent

7 stars

Best use case

amoa-label-taxonomy is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Use when applying GitHub labels. Trigger with label query or assignment requests. Loaded by ai-maestro-orchestrator-agent-main-agent

Teams using amoa-label-taxonomy should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/amoa-label-taxonomy/SKILL.md --create-dirs "https://raw.githubusercontent.com/Emasoft/ai-maestro-orchestrator-agent/main/skills/amoa-label-taxonomy/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/amoa-label-taxonomy/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How amoa-label-taxonomy Compares

Feature / Agentamoa-label-taxonomyStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Use when applying GitHub labels. Trigger with label query or assignment requests. Loaded by ai-maestro-orchestrator-agent-main-agent

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# AMOA Label Taxonomy

## Overview

GitHub label taxonomy for AI Maestro orchestration. Format: `<category>:<value>` with cardinality rules.

## Prerequisites

GitHub CLI (`gh`) configured; AGENT_OPERATIONS.md for context.

## Instructions

1. Identify label category and check cardinality in usage-rules.md
2. If updating, remove conflicting labels first (`assign:*`, `status:*`)
3. Apply via `gh issue edit` and verify
4. Every issue MUST have: `status:*`, `priority:*`, `type:*`

Copy this checklist and track your progress:

- [ ] Check cardinality rules. See: [references/usage-rules.md](./references/usage-rules.md)
  <!-- TOC: Label Cardinality | Label Lifecycle | Common Mistakes to Avoid -->
- [ ] Remove conflicting labels, apply new label via `gh` CLI
- [ ] Verify label applied correctly

Categories: `assign:`(0-1) `status:`(1) `priority:`(1) `type:`(1) `component:`(1+) `effort:`(1) `platform:`(0+) `toolchain:`(0+) `review:`(0-1). Details: [label-categories-detailed.md](./references/label-categories-detailed.md)
<!-- TOC: Assignment Labels (`assign:*`) | Rules | Assignment Authority | Conflict Resolution | Status Labels (`status:*`) | Rules | Status Workflow | Priority Labels (`priority:*`) | Rules | Type Labels (`type:*`) | Rules | Component Labels (`component:*`) | Rules | Effort Labels (`effort:*`) | Rules | Platform Labels (`platform:*`) | Rules | Toolchain Labels (`toolchain:*`) | Rules | Review Labels (`review:*`) | Rules -->

Kanban: `backlog`→`todo`→`in-progress`→`ai-review`→`human-review`→`merge-release`→`done` (+`blocked`). CLI ref: [cli-commands.md](./references/cli-commands.md)
<!-- TOC: Create Labels | Query Labels | Update Labels | Validate Label Cardinality -->

## Output

Confirmations, query tables, validation reports. See: [references/error-handling-and-output.md](./references/error-handling-and-output.md)
<!-- TOC: Error Handling | Output Formats | Colors Reference -->

## Examples

See: [references/examples.md](./references/examples.md)
<!-- TOC: Example 1: Assign Task to Agent | Example 2: Update Status During Workflow | Example 3: Query Issues by Multiple Labels | Example 4: Validate Label Cardinality -->

**Input:** `gh issue edit 42 --remove-label "assign:implementer-1" --add-label "assign:implementer-2"`
**Output:** `Updated issue #42`

## Error Handling

See: [references/error-handling-and-output.md](./references/error-handling-and-output.md)
<!-- TOC: Error Handling | Output Formats | Colors Reference -->

## Resources

- [label-categories-detailed.md](./references/label-categories-detailed.md)
- [cli-commands.md](./references/cli-commands.md)
- [examples.md](./references/examples.md)
- [usage-rules.md](./references/usage-rules.md)
- [error-handling-and-output.md](./references/error-handling-and-output.md)

Related Skills

amoa-verification-patterns

7
from Emasoft/ai-maestro-orchestrator-agent

Use when verifying implementations. Trigger with verification, testing, or evidence requests. Loaded by ai-maestro-orchestrator-agent-main-agent

amoa-two-phase-mode

7
from Emasoft/ai-maestro-orchestrator-agent

Use when running Plan-then-Execute workflows. Trigger with plan-execute or two-phase requests. Loaded by ai-maestro-orchestrator-agent-main-agent

amoa-task-distribution

7
from Emasoft/ai-maestro-orchestrator-agent

Use when distributing tasks. Trigger with task assignment requests. Loaded by ai-maestro-orchestrator-agent-main-agent

amoa-remote-agent-coordinator

7
from Emasoft/ai-maestro-orchestrator-agent

Use when coordinating remote AI agents via AI Maestro messaging. NOT for human coordination. Trigger with agent delegation or multi-agent requests. Loaded by ai-maestro-orchestrator-agent-main-agent

amoa-progress-monitoring

7
from Emasoft/ai-maestro-orchestrator-agent

Use when monitoring agent progress. Trigger with status check or stall detection requests. Loaded by ai-maestro-orchestrator-agent-main-agent

amoa-plan-phase

7
from Emasoft/ai-maestro-orchestrator-agent

Use when running Plan Phase of two-phase mode. Trigger with planning, requirements, or plan approval requests. Loaded by ai-maestro-orchestrator-agent-main-agent

amoa-orchestration-patterns

7
from Emasoft/ai-maestro-orchestrator-agent

Use when breaking down tasks for human developers. Trigger with task decomposition requests. Loaded by ai-maestro-orchestrator-agent-main-agent

amoa-orchestration-loop

7
from Emasoft/ai-maestro-orchestrator-agent

Use when running the orchestrator loop or managing stop hook behavior. Trigger with loop, stop hook, or state file requests. Loaded by ai-maestro-orchestrator-agent-main-agent

amoa-module-sync

7
from Emasoft/ai-maestro-orchestrator-agent

Use when syncing modules with GitHub Issues or troubleshooting module state. Trigger with sync, issue, or module troubleshooting requests. Loaded by ai-maestro-orchestrator-agent-main-agent

amoa-module-management

7
from Emasoft/ai-maestro-orchestrator-agent

Use when managing modules during Orchestration Phase. Trigger with module add, modify, or reassign requests. Loaded by ai-maestro-orchestrator-agent-main-agent

amoa-module-lifecycle

7
from Emasoft/ai-maestro-orchestrator-agent

Use when adding, modifying, removing, prioritizing, or reassigning modules. Trigger with module CRUD requests. Loaded by ai-maestro-orchestrator-agent-main-agent

amoa-messaging-templates

7
from Emasoft/ai-maestro-orchestrator-agent

Use when sending inter-agent messages. Trigger with task assignment, status report, or escalation needs. Loaded by ai-maestro-orchestrator-agent-main-agent