agentleFS
Sign inStart free
JustineDevsJustineDevs/meta-architect/skills/build/SKILL.md

build

Skill5 starsChanged 7 months agoMITView on GitHub

Use when the user wants to decide whether implementation is ready, what remains blocked, and what the exact next build step should be.

156 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use backprop, finances 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.
  • JuliusBrusseeSkill

    backprop

    Bug → spec protocol. When a bug is found or a test fails, trace the cause, decide whether a new §V invariant would catch recurrence, append to §B. This is the one non-obvious thing SDD does that plan-then-execute doesn't. Triggers on test failure, bug report, post-mortem, or explicit user ask.

    Also in 4 projects that use this

  • GerardoRdz96Skill

    finances

    Use when Gera talks about his money — logging an expense ("I spent X on Y"), checking where he stands this pay-period, closing a period, planning debt payoff, onboarding his financial picture, or asking for budgeting/finance opinions. Servy's financial brain. Triggers — "I spent", "log this expense", "where am I this period", "close the period", "how's my budget", "debt plan", "should I pay off", "finances onboard", "/finances".

    Also in 3 projects that use this

  • cpiprintSkill

    favicon

    Generate favicons from a source image

    Also in 3 projects that use this

  • madeehahassanSkill

    Go-Live

    Pre-launch checklist. Use before making any app public, sharing a link externally, or announcing a product launch. Adapts to Claude Code, claude.ai, and Cowork.

    Also in 3 projects that use this

  • JuliusBrusseeSkill

    deepen

    Optional design-improvement pass for when you have spare usage to drain. Finds the shallowest modules in the code the spec touches, researches a deeper design, and proposes refactors that shrink interfaces and hide decisions — behavior held constant, tests green before and after. Proposes §I/§V/§T edits, never silent rewrites. Triggers when the user says "deepen this", "improve the design", "this module feels shallow", "pull complexity down", "use spare budget on the codebase", or invokes /ck:deepen. Leans on the codebase-design skill's deep-module vocabulary when present.

    Also in 3 projects that use this

  • synaptiaiSkill

    gate

    Create a BDSK review_gate artifact. Defines a checkpoint that controls whether generated output may proceed toward acceptance. Use when defining quality, security, or scope gates for execution plans.

    Also in 5 projects that use this

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 7 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 143 edited versions we read keep these.

  • 7

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

    Use this skill inside Codex to convert the earlier review lanes into an implementation-ready decision.

    line 8
  2. Distinctive:

    test and verification expectations

    line 18
  3. Distinctive:

    Do not claim readiness if architecture, evidence, logic, security, or DX/UX gaps remain unresolved.

    line 24
  4. Distinctive:

    Keep the recommended build slice small, testable, and reversible.

    line 25
  5. Very specific:

    Treat $build as the sole owner of .ma/plans/build.md and build_status.

    line 26
  6. Distinctive:

    If the user wants code immediately and the path is clear, end with a concrete implementation plan rather than more review prose.

    line 27
  7. Distinctive:

    Read the current architecture, evidence, security, UX, and logic decisions.

    line 31
  8. Distinctive:

    No build step may silently publish, deploy, delete, or rewrite user-owned state.

    line 47

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

Build

Use this skill inside Codex to convert the earlier review lanes into an implementation-ready decision.

Output

Produce:

  • current readiness verdict
  • blockers that still prevent implementation
  • the narrowest viable build slice
  • branch or worktree suggestions when relevant
  • bounded execution state when the build lane is already in progress
  • test and verification expectations
  • repair path when the bounded slice needs another pass
  • the exact next implementation step

Rules

  • Do not claim readiness if architecture, evidence, logic, security, or DX/UX gaps remain unresolved.
  • Keep the recommended build slice small, testable, and reversible.
  • Treat $build as the sole owner of .ma/plans/build.md and build_status.
  • If the user wants code immediately and the path is clear, end with a concrete implementation plan rather than more review prose.

Procedure

  1. Read the current architecture, evidence, security, UX, and logic decisions.
  2. Classify each unresolved item as a release blocker, a bounded implementation task, or accepted risk.
  3. Select one narrow slice with explicit inputs, changed surfaces, acceptance checks, and rollback boundary.
  4. Define the regression-first test shape and the exact verification commands.
  5. Hand the bounded slice to execution and keep unrelated cleanup out of scope.

Default evidence dossier

Use docs/reference/supply-chain-readiness.md for package, publish, deploy, and artifact work. Identify provenance, verification, promotion, rollback, and tamper-detection evidence before calling a release ready. Do not claim an SLSA level without matching evidence.

Quality bar

  • “Ready” means the slice is implementable and testable, not that every future feature is designed.
  • No build step may silently publish, deploy, delete, or rewrite user-owned state.
  • A blocked result includes the missing evidence and the smallest probe that can unblock it.

Example

For a plugin release, verify version alignment, package contents, endpoint health, imported skills, release notes, and rollback behavior before recommending publication.

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