ea-briefing
Skill1 starsChanged 2 months agoMITView on GitHub
Produce an Enterprise-Architecture briefing from a technical update or discussion, with governance questions; translate PL↔EN if the source and audience differ.
In this repository28 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- architect-reviewSkill
- article-writingSkill
- changelog-watchSkill
- coordinator-workersSkill
- cost-forecastSkill
- design-docSkill
- documentSkill
- estimateSkill
- eval-toolSkill
- gh-ticketsSkill
- headless-loopSkill
- interview-guideSkill
- job-supervisorSkill
- market-researchSkill
- meeting-notesSkill
- migration-planSkill
- obsidian-noteSkill
- plan-to-issuesSkill
- postmortemSkill
- readSkill
- release-notesSkill
- skill-stocktakeSkill
- slide-deckSkill
- status-reportSkill
- threat-modelSkill
- tradeoff-tableSkill
- zoom-outSkill
The file
Files
Turn $ARGUMENTS into a concise briefing for senior/Enterprise Architects:
context, what's proposed, key decisions, risks, and 3–5 sharp governance questions worth
raising. If the source language differs from the intended audience language, translate
faithfully (PL↔EN) and keep technical terms precise. Markdown only.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.