القائمة
Use when validating effort estimates, creating sub-issues, or ADR issues. Trigger with label taxonomy ops 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-ops |
| description | Use when validating effort estimates, creating sub-issues, or ADR issues. Trigger with label taxonomy ops request. Loaded by ai-maestro-architect-agent-main-agent |
| context | fork |
| user-invocable | false |
| agent | ai-maestro-architect-agent-main-agent |
Operational procedures for the AMAA label taxonomy: validating effort estimates, creating component sub-issues from epics, and creating Architecture Decision Record (ADR) issues.
gh) installed and authenticatedCopy this checklist and track your progress:
| Document | Content |
|---|---|
| op-validate-effort-estimate.md | Purpose, When to Use, Prerequisites, Procedure, Example, Effort Guidelines, Error Handling |
| op-create-sub-issues.md | Purpose, When to Use, Prerequisites, Procedure, Example, Description, Error Handling |
| op-create-adr-issue.md | Purpose, When to Use, Prerequisites, Procedure, Example, Status, Error Handling |
Example: gh issue edit 123 --remove-label "effort:s" --add-label "effort:m" after architecture reveals higher complexity.
| Issue | Fix |
|---|---|
| No effort label found | Recommend effort based on analysis |
| Duplicate ADR number | Re-query and increment |
| Too many sub-issues | Combine related tasks |
| Type | Description |
|---|---|
| Effort updates | CLI stdout confirmation |
| Sub-issue creation | New issue URLs |
| ADR issues | ADR issue URL with status |
See Reference Documents table above.