Architecture Pattern — Skills
Pattern: Architecture
Component: skills.md
Version: 1.3 | Updated: 2026-07-29
| Skill | Path | Why required |
|---|---|---|
| Architecture | skills/architecture.skill.md |
Scenario-governed design |
| Security | skills/security.skill.md |
Trust boundaries and threat notes |
| Planning | skills/planning.skill.md |
When design must become an executable plan |
Related agents
Skill activation triggers
Run Architecture when topology or quality-attribute scenarios are undecided. Run Security when trust boundaries or threat notes are missing. Hand off to Planning only after the ADR rejects alternatives explicitly.
Verification that skills worked
- ADR records at least one rejected alternative with rationale
- Quality-attribute scenarios are named, not implied
- Trust boundaries appear before implementation planning
Changelog
- 1.3 (2026-07-29): Architecture skill activation and verification rewritten for this envelope.
Version: AIES v1.0.0✏️ Edit this page on GitHub