skills.rest
AutumnsGrove
AutumnsGroveCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

eagle-architect

Design system architecture blueprints with service contracts, data schemas, and ADRs.

5|Updated Nov 22, 2025
Search Tags:#planning#architecture#documentation#system design#microservices#event-driven
One-click install
npx skills add https://github.com/AutumnsGrove/Lattice --skill eagle-architect
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: eagle-architect
Source: https://github.com/AutumnsGrove/Lattice/tree/main/.claude/skills/eagle-architect
Command: npx skills add https://github.com/AutumnsGrove/Lattice --skill eagle-architect

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps users design robust and scalable system architectures by providing a structured approach to understanding requirements, defining boundaries, and documenting decisions.

Core Features & Use Cases

  • Architectural Planning: Guides users through phases of soaring, surveying, designing, and blueprinting system architecture.
  • Decision Documentation: Emphasizes the creation of Architecture Decision Records (ADRs) for every major choice.
  • Use Case: When planning a new microservice, use this Skill to define its domain boundaries, communication patterns, and technology stack, ensuring it integrates well with the existing ecosystem.

Quick Start

Use the eagle-architect skill to design the architecture for a new user notification system.

Frequently Asked Questions about eagle-architect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design system architecture for a new microservice?▼

To design system architecture for a new microservice, you must define domain boundaries, communication patterns, data flow, and failure modes to ensure it integrates well with the existing ecosystem. This structured approach guides you through problem definition and scale constraints.

What is the best way to document architectural decisions for a software project?▼

The best way to document architectural decisions is by creating Architecture Decision Records (ADRs) for every major choice regarding patterns, service contracts, and technology stacks. This ensures every architectural constraint and reasoning is formally recorded.

When should I choose an event-driven architecture over a monolith?▼

You should choose an event-driven architecture over a monolith after mapping out your problem definition, scale requirements, and existing systems. This skill assists in evaluating these architectural patterns against your specific constraints and failure modes.

How do I create a comprehensive system blueprint including deployment diagrams and data schemas?▼

To create a comprehensive system blueprint, you must define API design principles, service contracts, data schemas, and deployment diagrams. This process involves surveying existing systems and blueprinting the chosen technology stack and data flow.

Related Skills

Explore More Software Engineering Skills→
pekralpekral

product-capability

Transform product requirements into engineering specifications with Laravel architectural constraints.

Community
Advanced
vxcozyvxcozy
3

architect

Convert audit findings into phased implementation blueprints with success criteria.

Community
Advanced
fjacquetfjacquet
1

finwiz-validation

Validate FinWiz outputs against Pydantic v2 strict schemas.

Community
Advanced
felix-howardfelix-howard

ck:ask

Orchestrate specialized advisors to analyze system design and technology choices.

Community
Advanced