Architect Agent (eaa-)
Version: 1.0.0
Overview
The Architect Agent handles design documents, requirements analysis, and architecture decisions. It creates specifications that the Orchestrator uses to coordinate implementation work.
Prefix: eaa- = Emasoft Architect Agent
Core Responsibilities
- Requirements Analysis: Gather and document requirements
- Design Documents: Create technical specifications and architecture docs
- API Research: Investigate APIs and integration points
- Planning: Break down work into implementable modules
- Hypothesis Verification: Test assumptions before committing to design
Components
Agents
| Agent | Description |
|---|
eaa-architect-main-agent.md | Main architect agent |
eaa-documentation-writer.md | Creates technical documentation |
eaa-api-researcher.md | Researches APIs and integrations |
eaa-modularizer-expert.md | Breaks work into modules |
eaa-planner.md | Creates implementation plans |
eaa-cicd-designer.md | Designs CI/CD pipelines and workflows |
Commands
| Command | Description |
|---|
eaa-start-planning | Start planning phase |
eaa-add-requirement | Add new requirement |
eaa-modify-requirement | Modify existing requirement |
eaa-remove-requirement | Remove requirement |
Skills
| Skill | Description |
|---|
eaa-design-lifecycle | Design document management |
eaa-requirements-analysis | Requirements patterns |
eaa-documentation-writing | Documentation skills |
eaa-api-research | API research patterns |
eaa-planning-patterns | Planning methodology |
eaa-hypothesis-verification | Test assumptions |
eaa-design-communication-patterns | Shared utilities |
eaa-cicd-design | CI/CD pipeline design patterns |
eaa-design-management | Design document management tools |
eaa-github-integration | GitHub integration patterns |
eaa-label-taxonomy | Label and tagging patterns |
eaa-modularization | Module decomposition patterns |
eaa-session-memory | Session context persistence |
Hooks
| Hook | Event | Description |
|---|
eaa-skill-activation | UserPromptSubmit | Activate relevant design skills |
Workflow
- Receives requirements from Assistant Manager
- Analyzes requirements and creates design documents
- Breaks work into implementable modules
- Creates handoff document for Orchestrator
- Reports completion to Assistant Manager
Output Artifacts
- Design documents (markdown)
- Module specifications
- API integration plans
- Architecture diagrams (mermaid)
- Handoff files for Orchestrator
Installation (Production)
Install from the Emasoft marketplace. Use --scope local to install only for this agent's directory only, or --scope global for all projects.
Role plugins are installed with --scope local inside the specific agent's working directory (~/agents/<agent-name>/). This ensures the plugin is only available to that agent.
# Add Emasoft marketplace (first time only)
claude plugin marketplace add emasoft-plugins --url https://github.com/Emasoft/emasoft-plugins
# Install plugin (--scope local = this agent's directory only, recommended)
claude plugin install emasoft-architect-agent@emasoft-plugins --scope local
# RESTART Claude Code after installing (required!)
Once installed, start a session with the main agent:
claude --agent eaa-architect-main-agent
Development Only (--plugin-dir)
--plugin-dir loads a plugin directly from a local directory without marketplace installation. Use only during plugin development.
claude --plugin-dir ./OUTPUT_SKILLS/emasoft-architect-agent
Validation
cd OUTPUT_SKILLS/emasoft-architect-agent
uv run python scripts/validate_plugin.py . --verbose
Emasoft
