Microsoft AzureKnown publisherAzure/agent-app-orchestrator/.github/skills/architecture-decision/SKILL.mdarchitecture-decision
Skill107 starsChanged 3 days agoMITView on GitHub
Conducts and records a verifiable Agent Landing Zone Orchestrator architectural decision. Use when a choice alters runtime strategy boundaries, contracts, identity, data, deployment, or operation with meaningful reversal cost.
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 27 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 20
Do not turn a framework, model, or Azure service preference into an architectural requirement.
“Common” is measured: kept by at least 6 in 10 of the 27 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Agent Landing Zone Orchestrator architectural decision
- Load the relevant
engineering-principlesreferences. - Define the user or operator outcome, constraints, affected repositories, and up to five prioritized characteristics with measurable thresholds.
- Compare at least two viable alternatives and the option of not changing.
- Evaluate FastAPI and runtime strategy boundaries, identity, authorization, data and conversation compatibility, retrieval and MCP trust, deployment, cost, operation, migration, and reversibility.
- Record the decision using the ADR template.
- Define fitness functions, adoption order, rollback or roll-forward, and a review trigger.
Do not turn a framework, model, or Azure service preference into an architectural requirement. GitHub Copilot engineering agents are not runtime agent dependencies. When evidence is missing, record a time-bounded investigation and its decision criterion instead of guessing.
Other versions30 projects use a version of this.
Word for word · 1
- Azure/gpt-rag-orchestrator★ 107100% same
Edited · 8
- Azure/agent-landing-zone★ 1.2k60% same
- Azure/GPT-RAG★ 1.2k60% same
- Azure/agent-app-ingestion★ 18845% same
- Azure/gpt-rag-ingestion★ 18845% same
- Azure/gpt-rag-mcp★ 2253% same
- Azure/bicep-ptn-aiml-landing-zone★ 1936% same
- Azure/agent-app-ui★ 1055% same
- Azure/gpt-rag-ui★ 1055% same
Wrote their own version · 21
- Donchitos/Claude-Code-Game-Studios★ 27ksame name
- pixel-cellar/Claude-Code-Game-Studios★ 324same name
- striderZA/OpenCodeGameStudios★ 93same name
- cenconq25/claude-code-app-studio★ 40same name
- CoralGame/Claude-Code-Game-Studios★ 19same name
- dawn840705/codex-code-studios★ 17same name
- khuynh22/agent-dev-team★ 9same name
- lilangMax/ClaudeCodeGameStudios★ 8same name
- hongyuanc/codex-game-studios★ 5same name
- gonimar/claude-web-studio★ 4same name
11 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Used alongsideProjects with it also use team-level, team-narrative and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
CoralGameSkillteam-level
Orchestrate level design team: level-designer + narrative-director + world-builder + art-director + systems-designer + qa-tester for complete area/level creation.
Also in 10 projects that use this
- CoralGameSkill
team-narrative
Orchestrate the narrative team: coordinates narrative-director, writer, world-builder, and level-designer to create cohesive story content, world lore, and narrative-driven level design.
Also in 10 projects that use this
lilangMaxSkillcreate-stories
Break a single epic into implementable story files. Reads the epic, its GDD, governing ADRs, and control manifest. Each story embeds its GDD requirement TR-ID, ADR guidance, acceptance criteria, story type, and test evidence path. Run after /create-epics for each epic.
Also in 9 projects that use this
- lilangMaxSkill
story-done
End-of-story completion review. Reads the story file, verifies each acceptance criterion against the implementation, checks for GDD/ADR deviations, prompts code review, updates story status to Complete, and surfaces the next ready story from the sprint.
Also in 9 projects that use this
- +8 more from lilangMax
In this repository6 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
- documentation-consistencySkill
- engineering-principlesSkill
- orchestrator-releaseSkill
- releaseSkill
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.