emasoft-architect-agent

Add a new requirement or module to the plan during Plan Phase

Modify an existing requirement or module specification during Plan Phase

Remove a pending requirement or module from the plan (only if not started)

Enter Plan Phase Mode - begin requirements gathering and planning before implementation

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

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

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

Writes and maintains project documentation. Requires AI Maestro installed.

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

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

Use when investigating external APIs, libraries, and services. Creates standardized API documentation with auth and endpoints. Trigger with API research or library investigation requests.

Use when designing CI/CD workflows and DevOps architecture. Trigger with CI/CD pipeline or GitHub Actions design requests.

Use when accessing shared utilities, templates, and constants across Architect Agent skills. Trigger with shared template access or common utility imports.

Use when creating, reviewing, or archiving design documents. Manages design lifecycle from draft to archival. Trigger with design creation, review, or archival requests.

Use when managing design documents. Trigger with design search, validation, or creation requests.

Use when writing module specs, API contracts, ADRs, or feature specs. Follows 6 C's quality framework. Trigger with technical documentation requests for modules or architecture.

Use when linking design documents to GitHub issues. Creates issues from designs and syncs status. Trigger with GitHub issue linking or design traceability requests.

Use when verifying claims through Docker experimentation. Applies TBV principle to test claims before relying on them. Trigger with experiment setup or claim verification.

GitHub label taxonomy reference for the Architect Agent. Use when designing architecture, identifying components, or recommending labels. Trigger with architecture label requests.

Use when designing modular systems, breaking up monoliths, or defining module boundaries and APIs. Trigger with modularization requests, system decomposition, or coupling analysis.

Use when creating architecture plans. Trigger with /plan project or design system requests.

Use when managing planning phase: start planning, track progress, manage requirements/modules, or approve plans. Trigger with /start-planning or /planning-status commands.

Architecture decision and design pattern persistence. Use when preserving architectural context across sessions or creating design handoffs. Trigger with session start.

1 hook across 1 event