agentleFS
Sign inStart free
aprameyakaprameyak/coding-skills/architecture-decision/SKILL.md

architecture-decision

Skill1 starsChanged 41 days agoMITView on GitHub

Capture architecture decisions as short ADRs. Use when choosing between significant technical approaches or recording why a design exists.

32 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects 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.
  • 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

  • Microsoft AzureSkill

    component-release

    Prepares a verifiable Agent Landing Zone UI release. Use for release branches, VERSION, changelog entries, tags, release notes, and compatibility evidence; never publish without explicit human approval.

    Also in 4 projects that use this

  • +7 more from lilangMax

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 30 edited versions we read keep these.

  • 3

    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:

    Use for choices that are costly to reverse: data stores, service boundaries, auth models, public APIs, event schemas.

    line 10
  2. Distinctive:

    Prefer reversible experiments when uncertainty is high.

    line 39
  3. Distinctive:

    Update status when superseded.

    line 40

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

Architecture Decision

When

Use for choices that are costly to reverse: data stores, service boundaries, auth models, public APIs, event schemas.

Template

# ADR-<n>: <title>

Status: proposed|accepted|superseded
Date: <YYYY-MM-DD>

## Context
<forces and constraints>

## Decision
<what we will do>

## Alternatives
- <option>: <why not>

## Consequences
- positive: ...
- negative: ...
- follow-ups: ...

Rules

  • One decision per ADR.
  • Be concrete; name systems and constraints.
  • Prefer reversible experiments when uncertainty is high.
  • Update status when superseded; do not rewrite history silently.

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.

Reviews can't be read right now.

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