wicked-garden-engineering-architecture

Architecture Skill

Design end-to-end solutions with clear patterns, decisions, and visual documentation.

For genuinely structural greenfield design (system boundaries, cross-cutting design trade-offs, full ADR sets), dispatch the wicked-garden-engineering-solution-architect fork skill.

Purpose

Move from requirements to implementable architecture through:

• Pattern selection and justification
• Technology stack decisions
• Cross-cutting concern planning
• Architectural Decision Records (ADRs)

Process

1. Gather Context

• Read outcome document
• Analyze requirements
• Identify constraints
• Understand scale needs

2. Select Patterns

Choose architectural style:

• Monolithic - Simple deployment, single codebase
• Microservices - Independent scaling, team autonomy
• Serverless - Event-driven, auto-scaling
• Event-Driven - Loose coupling, async
• Layered - Clear separation, traditional

3. Make Decisions

Recommend stack based on:

• Requirements fit
• Team expertise
• Ecosystem maturity
• Cost considerations

4. Document

Creates in phases/design/:

design/
├── architecture.md
├── decisions/
│   ├── 001-architecture-style.md
│   └── 002-tech-stack.md
└── diagrams/
    └── system-context.mmd

Output Format

See ADR Template for decision records.

See Architecture Template - Design and Architecture Template - Deployment for full structure.

Integration

With wicked-crew

Auto-engaged during design phase.

Publishes: [arch:design:completed:success]

With qe

Architecture informs test strategy:

• Critical paths
• Failure modes
• Performance targets

With native tasks

Track work with ADR links via native TaskCreate:

TaskCreate(
  subject="ADR-001",
  description="Reference: phases/design/decisions/001.md",
  metadata={
    "event_type": "task",
    "chain_id": "{project}.design",
    "source_agent": "solution-architect",
    "phase": "design"
  }
)