From ea-assistant
This skill should be used when the user asks to "start an EA engagement", "manage an EA project", "set up a new architecture engagement", "what phase are we in", "advance the ADM", "continue the engagement", "resume an EA project", or when working within any TOGAF ADM phase. Provides end-to-end lifecycle guidance for Enterprise Architecture engagements using TOGAF 10 as the backbone.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ea-assistant:ea-engagement-lifecycleThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill guides the management of Enterprise Architecture engagements from initiation through closeout using TOGAF 10 as the process backbone, with Zachman as the classification lens and ArchiMate as the notation language.
references/adm-phase-guide.mdreferences/adm-tailoring.mdreferences/context-loading.mdreferences/engagement-patterns.mdreferences/engagement-schema.mdreferences/engagement-types.mdreferences/facilitator-config.mdreferences/governance-framework.mdreferences/images/governance-cascade.pngreferences/images/governance-structure.pngreferences/migration-gap-catalogue.mdreferences/phase-constraints.mdreferences/phase-inputs-outputs.mdreferences/phase-transitions.mdreferences/scaffolding-map.mdreferences/write-protocol.mdThis skill guides the management of Enterprise Architecture engagements from initiation through closeout using TOGAF 10 as the process backbone, with Zachman as the classification lens and ArchiMate as the notation language.
Every EA engagement is stored as a folder under EA-projects/:
EA-projects/
├── {engagement-slug}/
│ ├── engagement.json
│ ├── CLAUDE.md # auto-generated pointer doc (refreshed on /ea-open)
│ ├── .claude/rules/ea-engagement.md # persistent session guardrails
│ ├── artifacts/ # phase-organized artifact files
│ │ ├── preliminary/ # Prelim: Architecture Principles, Engagement Charter
│ │ ├── requirements/ # Requirements: Register, Traceability Matrix
│ │ ├── phase-a/ # Phase A: Architecture Vision, SAoW, Stakeholder Map
│ │ ├── phase-b/ # Phase B: Business Architecture, Business Model Canvas, Gap Analysis
│ │ ├── phase-c-data/ # Phase C: Data Architecture, Gap Analysis (Data)
│ │ ├── phase-c-app/ # Phase C: Application Architecture, Gap Analysis (Application)
│ │ ├── phase-d/ # Phase D: Technology Architecture, Gap Analysis (Technology)
│ │ ├── phase-e/ # Phase E: Consolidated Gap Analysis, Architecture Roadmap, Transition Architectures
│ │ ├── phase-f/ # Phase F: Migration Plan
│ │ ├── phase-g/ # Phase G: Architecture Contract, Compliance Assessment
│ │ ├── phase-h/ # Phase H: Change Request
│ │ └── cross-cutting/ # Risk Register, Decision Register, ADR Register, Zachman
│ │ └── notes/ # unscoped notes (no active phase)
│ ├── diagrams/
│ ├── uploads/
│ └── ResearchAndReferences/
└── .archive/
Each phase folder contains a notes/ subfolder created on demand with three subdirectories:
notes/interviews/ — dated interview note files (interview-{artifact-id}-{YYYY-MM-DD}-v{N}.md)notes/brainstorm/ — brainstorm-notes.md (one file per phase, seeded on first use)notes/reviews/ — grill/review output files (grill-{artifact-id}-{skill}-{YYYY-MM-DD}.md)Use /ea-notes to list, view, edit, or delete notes across all phases.
Frontmatter phase: | Folder | Primary artifacts |
|---|---|---|
Prelim | artifacts/preliminary/ | Architecture Principles, Engagement Charter, Governance Framework |
Requirements | artifacts/requirements/ | Requirements Register, Traceability Matrix |
A | artifacts/phase-a/ | Architecture Vision, Statement of Architecture Work, Stakeholder Map |
B | artifacts/phase-b/ | Business Architecture, Business Model Canvas, Gap Analysis |
C-Data | artifacts/phase-c-data/ | Data Architecture, Gap Analysis (Data) |
C-App | artifacts/phase-c-app/ | Application Architecture, Gap Analysis (Application) |
D | artifacts/phase-d/ | Technology Architecture, Gap Analysis (Technology) |
E or E/F | artifacts/phase-e/ | Consolidated Gap Analysis, Architecture Roadmap, Transition Architectures |
F | artifacts/phase-f/ | Migration Plan |
G | artifacts/phase-g/ | Architecture Contract, Compliance Assessment, Implementation Governance Plan |
H | artifacts/phase-h/ | Change Request |
All or cross-cutting | artifacts/cross-cutting/ | Risk Register, Decision Register, ADR Register, Zachman Diagram |
{{phase}} | resolve from engagement.json → currentPhase at creation time | Gap Analysis, ADRs |
From artifacts/{phase-folder}/{artifact-id}.md:
| Target | Relative path |
|---|---|
| Diagram file | ../../diagrams/{name}.{ext} |
| Same-phase artifact | ./{artifact-id}.md |
| Different-phase artifact | ../{phase-folder}/{artifact-id}.md |
| Upload document | ../../uploads/{filename} |
| Research document | ../../ResearchAndReferences/{filename}.md |
Artifact frontmatter cross-reference fields: relatedArtifacts: [], diagrams: [], links: [] — populate these so /ea-engage-review can trace dependencies without parsing body content.
All static data is in references/. Read these rather than relying on memory:
references/engagement-schema.md — full engagement.json schema with field definitions and version historyreferences/phase-transitions.md — engagement/phase status values and state transition table with timestamp rulesreferences/engagement-types.md — engagement type definitions, domain table, and ADM phase mapreferences/write-protocol.md — ownership rules for each section of engagement.jsonreferences/facilitator-config.md — settings file format, style behaviour, and audience level referencereferences/adm-phase-guide.md — detailed inputs, outputs, and steps per ADM phasereferences/engagement-patterns.md — common patterns and anti-patternsreferences/scaffolding-map.md — engagement type/domain → artifact scaffolding mappingreferences/phase-inputs-outputs.md — input/output tables per phase with quality gatesreferences/phase-constraints.md — plugin-level per-phase constraints: required artifacts, ID rules, traceability rules, and blocking gates; read by ea-facilitator on phase entry, ea-interviewer at session start, and ea-consistency-checker during validationreferences/adm-tailoring.md — tailoring ADM for agile, programme, capability, and security contextsG-NNN) — where you want to be (qualitative)OBJ-NNN) — specific measurable targets with a deadlineSTR-NNN) — approaches; each links to goal/objective IDs via supportsreferences/engagement-schema.md for metric schema.EA-projects/{slug}/ and seed files from templates/seeds/engagement.json with all fields. Set phase applicability per references/engagement-types.md and references/scaffolding-map.mdreferences/scaffolding-map.md)currentPhase to Prelim; confirm and offer to begin Preliminary phaseEA-projects/*/engagement.json (excludes .archive/ dotdir)All editing is accessed through /ea-open next actions menu.
engagementType, architectureDomains.supports link; a metric without a linked direction item is an orphan. See references/engagement-schema.md.references/phase-transitions.md. Suggest advancing currentPhase when a phase is marked Complete.EA-projects/{slug}/ → EA-projects/.archive/{slug}/. Invisible in /ea-status and /ea-open..archive/. Blocked if active engagement with same slug exists.currentPhase in engagement.jsonstatus to In Progress; set startedAt if first entry (see references/phase-transitions.md)references/phase-constraints.md for the entering phase; surface any Blocking gaps to the user before starting workea-facilitator agent for facilitation; ea-artifact-templates skill for artifacts; ea-interviewer agent for interviews; /ea-publish for exportartifacts/status to Complete and completedAt timestamplastModified in engagement.json; offer to advance to the next recommended phaseArtifacts are populated from three sources only:
ea-document-ingestion skill)Any AI-generated or suggested content MUST be marked:
> 🤖 **AI Draft — Review Required**
> [suggested content here]
Unanswered fields: ⚠️ Not answered
Not applicable fields: ➖ Not applicable
Default answers accepted by user: value written + ✓ Default accepted
See references/write-protocol.md for the full ownership table. Key rules:
engagement.json fresh before writinglastModified on every writeoptOuts[], artifacts[], or analysis_runs — append onlyProvides 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.
npx claudepluginhub somtimz/plugins --plugin ea-assistant