agentleFS
seancabalseseancabalse/agentic-playbook/skills/architecture-review/SKILL.md

architecture-review

Skill0 starsChanged 15 days agoMITView on GitHub

Review a design or a change for structural fit: tenancy, access, data flow, sync and coupling. Use before a large feature or for a structural change.

84 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use create-stories, story-done 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.
  • 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 11 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 11 projects that use this

  • +10 more from lilangMax

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 76 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read first: the relevant ADRs, the Architecture & Data Model doc, AGENTS.md, and for a PR the diff plus the code it touches.

    line 13
  2. Distinctive:

    Tenancy and access: every new row and object is scoped to the tenant.

    line 18
  3. Distinctive:

    Performance shape: no always-on work, budgets known, heavy work off the UI thread.

    line 24

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

Playbook files named here: when the project has its own copy at .playbook/local/<same path>, use that copy instead.

Scope: $ARGUMENTS

Read first: the relevant ADRs, the Architecture & Data Model doc, AGENTS.md, and for a PR the diff plus the code it touches. Principles: ${CLAUDE_PLUGIN_ROOT}/principles/02-architecture.md and 09-data-and-migrations.md.

Check

  1. Fit with decisions: does it follow the ADRs? If it departs from one, is that intended (and then a new ADR is needed)?
  2. Tenancy and access: every new row and object is scoped to the tenant; access is enforced at the data layer with tests; server-only values are fetched online.
  3. Boundaries: one client per service; layers depend one way; no reaching into another feature's internals; shared rules have one home.
  4. Data flow: query keys scoped by tenant and by user; writes are idempotent with client ids; offline writes go through the durable queue if the product needs it; there's a single retry layer; live updates invalidate; nothing shows "empty" before data arrives.
  5. Time: UTC instants plus zones, calendar dates as dates, the shared time module, and entry in the zone where the event happens.
  6. Lifecycle: soft delete and purge, files follow rows, server-stamped fields, idempotent and re-plannable jobs.
  7. Product hooks: entitlement checks on costly creates, configuration as data, privacy by construction.
  8. Performance shape: no always-on work, budgets known, heavy work off the UI thread.
  9. Evolution: old clients keep working through the migration; the change is reversible or forward-fixable.

Output

  • Verdict: fits / fits with changes / needs an ADR first.
  • Findings, ranked: each with the concrete risk (scenario → consequence), the principle it breaks, and the suggested change. No style preferences.
  • Decisions needed: for the owner (product) or for an ADR (technical).
  • Offer to file the findings as tickets.

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.