agentleFS
tatashbartatashbar/Economic-Modeling-Studio/.agents/skills/gate-check/SKILL.md

gate-check

Skill4 starsChanged 6 days agoMITView on GitHub

Runs a phase gate: checks exit criteria for the current stage and returns PASS / CONCERNS / FAIL / NOT ASSESSED.

22 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use setup-engine, team-level 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

    setup-engine

    Configure the project's game engine and version. Pins the engine in CLAUDE.md, detects knowledge gaps, and populates engine reference docs via WebSearch when the version is beyond the LLM's training data.

    Also in 13 projects that use this

  • 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 12 projects that use this

  • lilangMaxSkill

    asset-spec

    Generate per-asset visual specifications and AI generation prompts from GDDs, level docs, or character profiles. Produces structured spec files and updates the master asset manifest. Run after art bible and GDD/level design are approved, before production begins.

    Also in 10 projects that use this

  • lilangMaxSkill

    create-control-manifest

    After architecture is complete, produces a flat actionable rules sheet for programmers — what you must do, what you must never do, per system and per layer. Extracted from all Accepted ADRs, technical preferences, and engine reference docs. More immediately actionable than ADRs (which explain why).

    Also in 10 projects that use this

  • +2 more from CoralGame
  • +5 more from lilangMax

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 21 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

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

    If a required input is ABSENT, that part is NOT ASSESSED — NO DATA: do not estimate or invent it.

    line 26
  2. Very specific:

    Collaboration: Follow .claude/docs/collaboration-protocol.md: ask questions first, present options, get approval before writing files, and …

    line 28
  3. Very specific:

    Read the gate definition in .claude/docs/phase-gates.md

    line 39
  4. Distinctive:

    Check every criterion against actual files.

    line 40
  5. Distinctive:

    Ask the economic-reasoning, methodology and model-risk specialists for a verdict on their criteria

    line 42
  6. Distinctive:

    Before the verdict is recorded: review blockers and owners

    line 46
  7. Distinctive:

    Every FOUND criterion cites a file

    line 60

“Common” is measured: kept by at least 6 in 10 of the 21 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
<!-- Generated from .claude/skills/gate-check/SKILL.md by tools/sync_agents.py. Edit the source, then run the script. -->

/gate-check — Gate Check

Category: Governance · Primary agent: project-planning-specialist

Runs a phase gate: checks exit criteria for the current stage and returns PASS / CONCERNS / FAIL / NOT ASSESSED.

Arguments: whatever the user wrote after the command name.

Purpose

Run a phase gate: check, criterion by criterion, whether the evidence for leaving the current stage exists in the project's files, collect specialist verdicts, and return an overall verdict with blockers, owners and next actions. A gate never passes by default; missing evidence means NOT ASSESSED.

Use it when a project wants to move from one stage to the next (concept, design, build, estimate, validate, operate), or before a milestone review.

Do not use it when the question is release approval for a model (/model-risk-review, /model-release).

Before you start

  1. Check required inputs. For each input below record FOUND or ABSENT (never 'assumed'):
    • Stage artifacts
    • studio-config.yaml If a required input is ABSENT, that part is NOT ASSESSED — NO DATA: do not estimate or invent it; name what is missing and which skill produces it. If all required inputs are absent, stop and say so.
  2. Check confidentiality. Identify the data classification level of the inputs (.claude/docs/confidentiality-and-ai-use.md). Do not proceed with restricted or confidential data in a way the policy does not allow.
  3. Collaboration. Follow .claude/docs/collaboration-protocol.md: ask questions first, present options, get approval before writing files, and update production/session-state/active.md after each approved section.

Agents

  • project-planning-specialist — primary agent; coordinates the work and integrates results
  • economic-reasoning-specialist — Frames the economic question and tests whether results make economic sense
  • modeling-methodology-specialist — Chooses methods and architecture across model families, sets code and data standards, and resolves technical trade-offs between traditional, structural and AI approaches
  • model-risk-governance-specialist — Defines model risk levels and validation depth, enforces builder-validator independence, governs AI/LLM use and recommends release or block

Each agent is defined in .claude/agents/<name>.md. If your tool runs subagents, run these agents as subagents, in parallel where the steps are independent; otherwise read each agent's file and apply its instructions in turn. Subagents only write to the paths named in your instructions.

Workflow

  1. Read the gate definition in .claude/docs/phase-gates.md
  2. Check every criterion against actual files; mark FOUND or ABSENT
    • Cite the file path for each FOUND item; for lego models include the manifest check status
  3. Ask the economic-reasoning, methodology and model-risk specialists for a verdict on their criteria
  4. Return an overall verdict with blockers, owners and next actions

Checkpoints with the user

  • Before the verdict is recorded: review blockers and owners

Common pitfalls

  • Passing on promises rather than files
  • Criteria marked FOUND without a file reference
  • Blockers without owners

Output

production/gates/<stage>-<date>.md

The gate record lists each criterion with FOUND or ABSENT and its evidence path, specialist verdicts, the overall verdict, blockers, owners and next actions.

Gate / verdict

  • Verdict 'NOT ASSESSED' if required evidence is absent — never a pass by default
  • Every FOUND criterion cites a file

Suggested next steps

  • /milestone-review

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.