Agent skill
gathering-architecture
The drum sounds. Eagle, Crow, Swan, and Elephant gather for system architecture. Use when designing major systems from vision to implementation.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/gathering-architecture-autumnsgrove-lattice
SKILL.md
Gathering Architecture π²π¦
The drum echoes high in the canopy. The Eagle soars above, seeing the forest's patterns. The Crow perches nearby, tilting its head at what others won't question. The Swan glides across the lake, elegant designs taking form. The Elephant moves below, building what was envisioned. Together they transform a clearing into a cathedral of codeβsystems that stand for seasons.
When to Summon
- Designing new systems or services
- Major architectural decisions
- Refactoring core infrastructure
- Creating platforms that other features build upon
- When vision, design, and implementation must align
Grove Tools for This Gathering
Use gw and gf throughout. Quick reference for architecture work:
# Orientation β understand the project before designing
gw context
# Explore the existing architecture
gf --agent search "pattern" # Find code patterns
gf --agent class "ServiceName" # Find class/component definitions
gf --agent routes # Map route structure
# Understand dependencies and change impact
gf --agent deps # Dependency graph
gf --agent impact "module" # Blast radius of changes
The Gathering
SUMMON β ORGANIZE β EXECUTE β VALIDATE β COMPLETE
β β² β² β² β
Receive Dispatch Animals Verify Architecture
Request Animals Work Design Defined
Animals Mobilized
- π¦ Eagle β Design system architecture from 10,000 feet
- π¦ββ¬ Crow β Challenge the design before it's cast in code
- π¦’ Swan β Write detailed technical specifications
- π Elephant β Implement the architectural foundation
Phase 1: SUMMON
The drum sounds. The canopy rustles...
Receive and parse the request:
Clarify the System:
- What problem does this solve?
- What are the scale requirements?
- What are the constraints?
- What's the growth trajectory?
Nature Metaphor:
"Every architecture needs a nature metaphor. What does this system resemble?
- Heartwood (core that holds everything)
- Wisp (gentle guiding light)
- Porch (place to gather and talk)
- Something else?"
Confirm:
"I'll mobilize an architecture gathering for: [system description]
This will involve:
- π¦ Eagle designing the high-level architecture
- π¦ββ¬ Crow challenging the design before it's cast in spec
- π¦’ Swan writing the detailed specification
- π Elephant implementing the foundation
Proceed with the gathering?"
Phase 2: ORGANIZE
The birds circle. The elephant waits below...
Dispatch in sequence:
Dispatch Order:
Eagle βββ Crow βββ Swan βββ Elephant
β β β β
β β β β
Design Challenge Write Build
System Design Spec Foundation
Dependencies:
- Eagle must complete before Crow (needs architecture to challenge)
- Crow must complete before Swan (design strengthened before specifying)
- Swan must complete before Elephant (needs detailed spec)
Phase 3: EXECUTE
The architecture takes form from sky to earth...
Execute each phase by loading and running each animal's dedicated skill:
π¦ EAGLE β DESIGN
Load skill: eagle-architect
Execute the full Eagle workflow focused on [the system being designed]. Handoff: architecture overview (system boundaries, component interactions, technology choices, scale constraints, nature metaphor, ADRs) β Swan for specification
π¦ββ¬ CROW β CHALLENGE
Load skill: crow-reason
Execute the Crow in Red Team mode against the Eagle's architecture overview. Challenge assumptions, find weak points, stress-test boundaries. The Crow's Roost summary feeds into the Swan β design decisions are strengthened before they're cast in spec. Handoff: strengthened architecture with Roost summary (challenges resolved, risks acknowledged) β Swan for specification
π¦’ SWAN β SPECIFY
Load skill: swan-design
Execute the full Swan workflow using the Eagle's architecture overview, strengthened by the Crow's challenges. Handoff: complete technical specification (API contracts, database schema, flow diagrams, implementation checklist) β Elephant for foundation building
π ELEPHANT β BUILD
Load skill: elephant-build
Execute the full Elephant workflow using the Swan's technical specification as the build plan. Handoff: working foundation (core infrastructure, base modules, API skeleton, database migrations, essential tests) β VALIDATE phase
Phase 4: VALIDATE
The structure stands. Each animal verifies their work...
Validation Checklist:
- Eagle: Architecture addresses all requirements
- Crow: Design challenged and strengthened
- Swan: Specification is complete and implementable
- Elephant: Foundation is solid and tested
Review Points:
After Eagle:
β Review architecture with stakeholders
β Confirm boundaries and trade-offs
β Approve before Crow challenges
After Crow:
β Review Roost summary
β Confirm which challenges are resolved vs accepted risks
β Approve strengthened design before Swan begins
After Swan:
β Review spec for completeness
β Verify all sections present
β Confirm implementation ready
After Elephant:
β Test foundation thoroughly
β Verify patterns established
β Confirm next features can build upon it
Phase 5: COMPLETE
The gathering ends. Architecture stands ready...
Completion Report:
## π² GATHERING ARCHITECTURE COMPLETE
### System: [Name]
### Animals Mobilized
π¦
Eagle β π¦ββ¬ Crow β π¦’ Swan β π Elephant
### Architecture Decisions
- **Pattern:** [e.g., Event-driven microservices]
- **Scale Target:** [e.g., 10k concurrent users]
- **Key Trade-offs:** [summary]
### Artifacts Created
- Architecture Overview (`docs/architecture/[system].md`)
- Technical Specification (`docs/specs/[system]-spec.md`)
- ADRs ([list])
- Foundation Code ([location])
- Base Tests ([location])
### Ready for
- Feature development on this foundation
- Team onboarding using the spec
- Future architecture reviews
### Time Elapsed
[Duration]
_The forest has a new landmark._ π²
Example Gathering
User: "/gathering-architecture Design the notification system"
Gathering execution:
-
π² SUMMON β "Mobilizing for: Notification system. Send email, push, SMS to users. Scale: millions of notifications/day."
-
π² ORGANIZE β "Sequence: Eagle (architecture) β Crow (challenge) β Swan (spec) β Elephant (foundation)"
-
π² EXECUTE β
- π¦ Eagle: "Event-driven: App emits events β Queue β Workers β Providers. Scales horizontally."
- π¦ββ¬ Crow: "Red Team mode. Challenged: operational complexity for small team, eventual consistency with account deletion, microservice gravity. Strengthened: modular monolith with clean service boundary, extract later."
- π¦’ Swan: "Complete spec incorporating Crow's strengthened position, with flow diagrams, API contracts, provider adapter interface"
- π Elephant: "Event bus, queue infrastructure, base notification service, database schema"
-
π² VALIDATE β "Architecture handles scale, spec complete, foundation tested"
-
π² COMPLETE β "Notification platform ready for feature development"
From vision to foundation, the forest grows. π²
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?