Magnus HedemarkandGitHub
8174e820e2
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>
2.0 KiB
Public Source Index and Transformation Boundary
This skill is an original, task-centered methodology. Public sources provide terminology and prompts for comparison; they are not reproduced as instructional text.
| Source | Use in this skill | URL |
|---|---|---|
| ISO/IEC/IEEE 42010 overview | Stakeholders, concerns, viewpoints, and architecture descriptions | https://www.iso.org/standard/74393.html |
| ArchiMate specification | Public notation vocabulary for relationships among motivation, strategy, business, application, and technology views | https://www.opengroup.org/archimate-forum/archimate-overview |
| TOGAF public overview | Enterprise architecture lifecycle vocabulary and governance context only | https://www.opengroup.org/togaf |
| Wardley Mapping public guide | Capability positioning and dependency conversation prompts; no prescribed map is reproduced | https://learnwardleymapping.com/ |
| Thoughtworks Technology Radar | Technology adoption and uncertainty vocabulary; portfolio governance remains with technology-radar |
https://www.thoughtworks.com/radar |
| W3C Web Content Accessibility Guidelines | Accessible information and communication requirements | https://www.w3.org/TR/WCAG22/ |
Transformation boundary
Purchased ebooks and the private synthesized comparison report may inform research only. This repository does not reproduce their prose, tables, diagrams, examples, taxonomies, chapter order, or distinctive presentation. The deliverable was written from user tasks, public sources, repository ownership boundaries, and fresh examples. Do not read or quote purchased ebooks while using or extending this skill.
The method keeps only cross-source decision pressures: connect capability to outcome, distinguish evidence from aspiration, choose a reachable transition, place authority near the decision while protecting enterprise coherence, and publish information that people can actually use. Future edits should be rewritten from the user task if they resemble a source's distinctive structure or wording.