claude

ai-maestro-architect-agent

Design documents, requirements analysis, architecture decisions - creates specifications. Requires AI Maestro for inter-agent messaging.

2 on GitHubby Emasoftv2.17.21MITupdated 1 month ago

Not in a marketplace yet, so it loads for one session with --plugin-dir.

Plugin ai-maestro-architect-agent in Emasoft/ai-maestro-architect-agent. Commands read from the repo's manifest — 1 month ago.

This plugin runs code on your machine — its hooks fire automatically on events like tool use. The exact commands are listed below; read them before installing.

What it installs

Skills (27)

  • amaa-api-research-ops

    Use when needing API research scenarios or collaboration patterns. Trigger with API research ops request. Loaded by ai-maestro-architect-agent-main-agent

  • amaa-api-research

    Use when researching external APIs, libraries, and services. Trigger with API research request or library investigation task. Loaded by ai-maestro-architect-agent-main-agent

  • amaa-cicd-design-ops

    Use when debugging CI/CD, scripting with GH CLI, or referencing templates. Trigger with CI/CD ops or debugging request. Loaded by ai-maestro-architect-agent-main-agent

  • amaa-cicd-design

    Use when designing CI/CD pipelines, GitHub Actions, or release automation. Trigger with CI/CD design request or pipeline task. Loaded by ai-maestro-architect-agent-main-agent

  • amaa-design-communication-patterns-ops

    Use when handling edge cases or shared operations in architect communication. Trigger with communication ops request. Loaded by ai-maestro-architect-agent-main-agent

  • amaa-design-communication-patterns

    Use when implementing inter-agent messaging or design document protocols. Trigger with communication pattern or messaging request. Loaded by ai-maestro-architect-agent-main-agent

  • amaa-design-lifecycle-ops

    Use when applying judgment guidelines, success criteria, or handoff formats. Trigger with lifecycle ops request. Loaded by ai-maestro-architect-agent-main-agent

  • amaa-design-lifecycle

    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

  • amaa-design-management-ops

    Use when validating design documents or troubleshooting issues. Trigger with design management ops request. Loaded by ai-maestro-architect-agent-main-agent

  • amaa-design-management

    Use when creating, searching, or validating design documents. Trigger with document management or UUID generation request. Loaded by ai-maestro-architect-agent-main-agent

  • amaa-documentation-writing-ops

    Use when writing API contracts, ADRs, feature specs, or quality checks. Trigger with documentation ops request. Loaded by ai-maestro-architect-agent-main-agent

  • amaa-documentation-writing

    Use when writing module specs, API contracts, ADRs, or feature docs. Trigger with documentation writing or spec creation request. Loaded by ai-maestro-architect-agent-main-agent

  • amaa-github-integration-ops

    Use when troubleshooting GitHub integration or managing edge cases. Trigger with GitHub ops request. Loaded by ai-maestro-architect-agent-main-agent

  • amaa-github-integration

    Use when syncing designs to GitHub issues or managing project boards. Trigger with GitHub integration or issue sync request.

  • amaa-hypothesis-verification-ops

    Use when applying multiplicity rule or formatting experiment outputs. Trigger with verification ops request. Loaded by ai-maestro-architect-agent-main-agent

  • amaa-hypothesis-verification

    Use when verifying technical claims through Docker-isolated experiments. Trigger with hypothesis test or experiment request. Loaded by ai-maestro-architect-agent-main-agent

  • amaa-label-taxonomy-ops

    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

  • amaa-label-taxonomy

    Use when managing GitHub labels for the Architect Agent: component, effort, type, and priority labels. Trigger with label management or taxonomy request. Used on demand by ai-maestro-architect-agent-main-agent

  • amaa-modularization-ops

    Use when analyzing dependencies, planning migration, or testing modules. Trigger with modularization ops request. Loaded by ai-maestro-architect-agent-main-agent

  • amaa-modularization

    Use when decomposing systems into modules with clear boundaries. Trigger with modularization or module boundary request. Loaded by ai-maestro-architect-agent-main-agent

  • amaa-planning-patterns-ops

    Use when enforcing plans, verifying requirements, or linking to GitHub. Trigger with planning ops request. Loaded by ai-maestro-architect-agent-main-agent

  • amaa-planning-patterns

    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

  • amaa-prrd-trdd-kanban

    ARCHITECT's role in the PRRD / TRDD / Kanban workflow. Use when ARCH shapes a proto-TRDD into a full TRDD, decides whether to split (1→N), group (N→1), or pass-through, authors all the verification / impact / delivery frontmatter, and writes the prose body with acceptance criteria.

  • amaa-requirements-analysis-ops

    Use when troubleshooting requirements analysis or needing quick reference. Trigger with requirements ops request. Loaded by ai-maestro-architect-agent-main-agent

  • amaa-requirements-analysis

    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

  • amaa-session-memory-ops

    Use when recording stack choices, constraints, or managing handoffs. Trigger with session memory ops request. Loaded by ai-maestro-architect-agent-main-agent

  • amaa-session-memory

    Use when persisting decisions, patterns, and constraints across sessions. Trigger with session memory or handoff request. Loaded by ai-maestro-architect-agent-main-agent

Slash commands (4)

  • /ai-maestro-architect-agent:amaa-add-requirement

    Add a requirement or module to the plan

  • /ai-maestro-architect-agent:amaa-modify-requirement

    Modify an existing requirement or module spec

  • /ai-maestro-architect-agent:amaa-remove-requirement

    Remove a pending requirement or module from plan

  • /ai-maestro-architect-agent:amaa-start-planning

    Enter Plan Phase for requirements and design

Subagents (6)

  • ai-maestro-architect-agent-main-agent

    Architect main agent - design documents, requirements, architecture decisions. Requires AI Maestro installed.

  • amaa-api-researcher

    Researches API documentation and integration patterns. Requires AI Maestro installed.

  • amaa-cicd-designer

    Designs CI/CD pipelines, GitHub Actions, and deployment architecture. Requires AI Maestro installed.

  • amaa-documentation-writer

    Writes and maintains project documentation. Requires AI Maestro installed.

  • amaa-modularizer-expert

    Decomposes monolithic code into modular, reusable components. Requires AI Maestro installed.

  • amaa-planner

    Creates implementation plans from requirements with step-by-step breakdown. Requires AI Maestro installed.

Hooks (1)

  • Stop

    python3

View source on GitHub

Maintain ai-maestro-architect-agent?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex pluginslisted