agentleFS
Sign inStart free
Microsoft AzureKnown publisherAzure/gpt-rag-ui/.github/skills/architecture-decision/SKILL.md

architecture-decision

Skill10 starsChanged 13 days agoMITView on GitHub

Conducts and records a verifiable Agent Landing Zone UI architectural decision. Use when a choice alters boundaries, contracts, identity, sessions, persistence, accessibility, deployment, or operation with meaningful reversal cost.

32 other projects use a version of this, 9 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use team-level, team-narrative and 9 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.
  • CoralGameSkill

    team-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

  • lilangMaxSkill

    create-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

  • +7 more from lilangMax

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 29 edited versions we read keep these.

  • 2

    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
  1. Distinctive:

    Do not turn a tool or framework preference into an architectural requirement.

    line 20
  2. Distinctive:

    When evidence is missing, record a time-bounded investigation and its decision criterion instead of guessing.

    line 21

“Common” is measured: kept by at least 6 in 10 of the 29 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Agent Landing Zone UI architectural decision

  1. Load the relevant engineering-principles references.
  2. Define context, constraints, affected users and systems, and up to five prioritized characteristics with measures.
  3. Compare at least two viable alternatives and the option of not changing.
  4. Evaluate identity, authorization, session isolation, accessibility, backend compatibility, persistence, cost, operation, migration, and reversibility.
  5. Record the decision under docs/adr/ using the ADR template.
  6. Define fitness functions, adoption order, rollback or roll-forward, and a review trigger.

Do not turn a tool or framework preference into an architectural requirement. When evidence is missing, record a time-bounded investigation and its decision criterion instead of guessing.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free