mirror of
https://github.com/magnus919/agent-skills.git
synced 2026-09-11 19:47:12 +03:00
feat: add enterprise architecture methodology (#359)
Add capability and portfolio mapping, state transitions, operating models, decision rights, stakeholder information, templates, evals, and neighboring-owner routing.\n\nAI-assisted: Jasper orchestrated implementation and verification with OpenCode. Signed-off-by: Magnus Hedemark <magnus919@pm.me>
This commit is contained in:
@@ -15,7 +15,7 @@ CTO methodology for making technology decisions, governing architecture, measuri
|
||||
|
||||
## When Not to Use
|
||||
|
||||
- Route enterprise capability maps, operating-model design, and current/target-state roadmaps to the appropriate enterprise-architecture owner. This skill stays focused on technology portfolio posture and governance mechanics; use [`software-architecture`](../software-architecture/SKILL.md) for system-level target design.
|
||||
- Route enterprise capability maps, operating-model design, and current/target-state roadmaps to [`enterprise-architecture`](../enterprise-architecture/SKILL.md). This skill stays focused on technology portfolio posture and governance mechanics; use [`software-architecture`](../software-architecture/SKILL.md) for system-level target design.
|
||||
- Route the durable record of one consequential decision to `adr-authoring`; use this skill to choose the governance path and connect the decision to standards or radar feedback.
|
||||
- Route system design and code changes to the relevant engineering skill, security requirements and threat modeling to `secure-software-engineering`, and live operations or SLO work to `site-reliability-engineering`.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user