From ea-assistant
This skill should be used when the user asks to "create an artifact", "generate the architecture vision", "start a new artifact from a template", "what template should I use", "populate this artifact", or when any TOGAF artifact needs to be created or populated. Provides template selection, placeholder conventions, and guidance text marking standards for all EA artifacts.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ea-assistant:ea-artifact-templatesThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
All EA artifacts are created from templates stored in the plugin's `templates/` directory. Templates use a consistent structure with clearly marked guidance, placeholder tokens, and answer state markers.
All EA artifacts are created from templates stored in the plugin's templates/ directory. Templates use a consistent structure with clearly marked guidance, placeholder tokens, and answer state markers.
Every artifact template includes a taxonomy: block in its YAML frontmatter. Use references/taxonomy.md as the canonical reference for all valid values and assignment rules.
taxonomy:
domain: Cross-cutting # Business | Data | Application | Technology | Cross-cutting
category: Strategy # Strategy | Analysis | Design | Planning | Governance | Register
audience: Executive # Executive | Business | Architecture | Delivery | Governance | All
layer: Motivation # Motivation | Baseline | Target | Transition | Governance | Reference
sensitivity: Internal # Internal | Confidential | Restricted
tags: [vision, goals, phase-a]
When creating a non-standard artifact, assign taxonomy values using references/taxonomy.md. The taxonomy block is a T1-10 compliance requirement — all artifacts must have it.
All unfilled fields use double-brace tokens:
{{field_name}} — simple value
{{stakeholder_name}} — named entity
{{YYYY-MM-DD}} — date-only field (startDate, decisionDate, file names)
{{YYYY-MM-DDTHH:MM:SSZ}} — timestamp field (lastModified, createdAt, lastUpdated)
{{artifact_ref}} — reference to another artifact
Guidance explaining what a section means is marked with HTML comments so it is invisible in rendered output but visible in source:
<!-- GUIDANCE:
Describe the high-level intent and scope of this section.
This text is for the author and should NOT appear in the final deliverable.
Remove or leave as-is — it will not render in Word or HTML exports.
-->
| State | Marker |
|---|---|
| Answered | Value written directly |
| Not answered | ⚠️ Not answered |
| Not applicable | ➖ Not applicable |
| Opted out | ⊘ Opted out or ⊘ Opted out — {reason} |
| AI-suggested draft | > 🤖 **AI Draft — Review Required** blockquote |
| Default accepted | value + ✓ Default accepted |
| Source document | value + 📎 Source: uploads/{filename} |
Opted out vs. Not answered: ⊘ Opted out is an explicit, deliberate choice — the user decided this question or artifact is out of scope for their needs. The reason is recorded in engagement.json under optOuts[] and surfaced in status reports. ⚠️ Not answered is a temporary skip — the field may still be filled in later.
Used exclusively in Appendix A3 decision rows to track the governance state of each decision:
| State | Marker | Meaning |
|---|---|---|
| Provisional | 🔄 Provisional | Recorded but not yet reviewed or owned |
| Awaiting Verification | ⏳ Awaiting Verification | Assigned to an owner; pending their confirmation |
| Verified | ✓ Verified | Owner has confirmed the decision is correct |
| Under Vote | 🗳️ Under Vote | Submitted to stakeholders for a formal vote |
| Voted | ✅ Voted | Decision carried by stakeholder vote |
| Fiat | 👑 Fiat | Decided by a senior decision maker without vote |
| Returned | ↩️ Returned | Sent back for rework by approver or facilitator |
Every artifact that supports a Decision Log uses this standard table in ## Appendix A3 — Decision Log:
### Appendix A3 — Decision Log
| Item | Value | State | Captured By | Owner | Authority | Domain | Cost | Impact | Risk | Subject | Date |
|---|---|---|---|---|---|---|---|---|---|---|---|
| {{item}} | {{value}} | 🔄 Provisional | {{facilitator}} | {{owner}} | Strategic / Tactical / Operational | Business / Data / Application / Technology / Cross | High / Med / Low / TBD | High / Med / Low / TBD | High / Med / Low / TBD | {{subject_tag}} | {{date}} |
Field definitions:
| Field | Values | Meaning |
|---|---|---|
| Authority | Strategic / Tactical / Operational | Strategic = enterprise-wide long-term commitment; Tactical = engagement-scoped medium-term; Operational = implementation detail short-term |
| Domain | Business / Data / Application / Technology / Cross | Which architecture domain this decision primarily affects |
| Cost | High / Med / Low / TBD | Resource or time commitment required to execute this decision |
| Impact | High / Med / Low / TBD | Business or architecture impact if this decision stands or changes |
| Risk | High / Med / Low / TBD | Risk of making this decision incorrectly or reversing it later |
| Subject | Free text | Short tag (e.g. "Cloud strategy", "Data governance", "API design") for topic-based filtering |
A3 rows are the source data for /ea-decisions.
Every primary artifact (Architecture Vision, all domain architectures, Gap Analysis, Architecture Roadmap, Statement of Architecture Work, and Migration Plan) includes this appendix in ## Appendix A4 — Stakeholder Concerns & Objections:
### Appendix A4 — Stakeholder Concerns & Objections
| ID | Concern | Raised By | Category | Status | Response | Action / Owner |
|---|---|---|---|---|---|---|
| *(no concerns recorded)* | — | — | — | — | — | — |
Field definitions:
| Field | Values | Meaning |
|---|---|---|
| ID | CON-NNN | Concern identifier — sequential within the engagement across all artifacts |
| Concern | Free text | The objection, question, or challenge as it was raised — verbatim where possible |
| Raised By | Free text | Source: stakeholder name/role (e.g. "CIO"), "grill-me-boardroom", "Architecture Review Board", "Sponsor workshop", etc. |
| Category | Scope / Goal / Approach / Feasibility / Risk / Stakeholder / Other | The type of concern |
| Status | Addressed / Partially Addressed / Requires Attention | Whether the concern has been resolved |
| Response | Free text or artifact/section reference | Where in this artifact (or another) the concern is answered (e.g. "§3 Goals — G-001 scoped to exclude retail domain"). Leave blank if Requires Attention |
| Action / Owner | Free text | What needs to happen and who is responsible — only for Requires Attention items. Leave — for Addressed items |
Status rules:
Action / Owner to —/ea-concerns and may be escalated to the Risk Register as RIS-NNN entriesA4 rows are the source data for /ea-concerns.
Every artifact includes a status block at the top:
---
artifact: Architecture Vision
engagement: {{engagement_name}}
phase: A
status: Draft
reviewStatus: Not Reviewed
version: 0.1
lastModified: {{YYYY-MM-DDTHH:MM:SSZ}}
---
All TOGAF artifacts are in scope. Templates are stored in the plugin's templates/ directory:
| Template File | Artifact | ADM Phase |
|---|---|---|
engagement-charter.md | Engagement Charter | Prelim |
governance-framework.md | Governance Framework | Prelim |
architecture-principles.md | Architecture Principles | Prelim / A |
stakeholder-map.md | Stakeholder Map | Prelim / A |
architecture-vision.md | Architecture Vision | A |
statement-of-architecture-work.md | Statement of Architecture Work | A |
communications-plan.md | Communications Plan | A |
architecture-definition-document.md | Architecture Definition Document | A (skeleton) → F (final) |
business-model-canvas.md | Business Model Canvas | B |
business-architecture.md | Business Architecture | B |
data-architecture.md | Data/Information Architecture | C |
application-architecture.md | Application Architecture | C |
technology-architecture.md | Technology Architecture | D |
gap-analysis.md | Gap Analysis (domain) | B, C-Data, C-App, D |
consolidated-gap-analysis.md | Consolidated Gap Analysis | E |
transition-architectures.md | Transition Architectures | E / F |
architecture-roadmap.md | Architecture Roadmap | E / F |
migration-plan.md | Migration Plan | F |
implementation-governance-plan.md | Implementation Governance Plan | G |
architecture-contract.md | Architecture Contract | G |
compliance-assessment.md | Compliance Assessment | G |
change-request.md | Architecture Change Request | H |
change-register.md | Change Register | H (generated by /ea-changes) |
requirements-register.md | Architecture Requirements Register | Requirements |
traceability-matrix.md | Requirements Traceability Matrix | Requirements |
architecture-decision-record.md | Architecture Decision Record | All phases |
adr-register.md | ADR Register | All phases (generated by /ea-adrs) |
risk-register.md | Risk Register | All phases (generated by /ea-risks) |
zachman-diagram.md | Zachman Diagram | All phases (generated by /ea-zachman) |
decision-register.md | Decision Register | All phases (generated by /ea-decisions) |
consolidated-report.md | Consolidated Architecture Report | All phases |
EA-projects/{slug}/artifacts/{phase-folder}/{artifact-id}.md — derive {phase-folder} from the Phase Folder Mapping table in ea-artifact.mdengagement.json (name, sponsor, organisation)ea-document-ingestion){{field_name}} placeholdersengagement.json under artifacts[]When populating an artifact via interview:
{{...}})ea-interviewer agent⚠️ Not answered)➖ Not applicable)interviews/Guidance text in templates serves two purposes:
Guidance text is ALWAYS wrapped in <!-- GUIDANCE: ... --> HTML comments.
It must NEVER be removed automatically — the author decides whether to keep or remove it.
It does NOT appear in Word or HTML exports (HTML comments are not rendered).
references/artifact-descriptions.md — Purpose, audience, and contents of each TOGAF artifactreferences/template-authoring-guide.md — How to write and extend templatesreferences/ea-concepts.md — Canonical definitions and TOGAF/ArchiMate alignment for Principle, Goal, Objective, Strategy, Plan, and Risk. Load this when concept confusion is detected during interviews or artifact population.references/compliance-check.md — Compliance rules (Tier 1/2/3), check procedure, remediation actions for Option 1 (achieve compliance) and Option 2 (accept as-is with defaults). Load this whenever an artifact is opened for interview, review, or viewing.npx claudepluginhub somtimz/plugins --plugin ea-assistantProvides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.