agentleFS
Sign inStart free
iwesysiwesys/IWE/.claude/skills/integration-gate/SKILL.md

integration-gate

Skill0 starsChanged 24 days agoMITView on GitHub

IntegrationGate — a mandatory checklist (4 steps) for designing a new

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    Create or update DP.SC.NNN in PACK-digital-platform/.../08-service-clauses/.

    line 35
  2. Very specific:

    Implementation: Only after steps (1)–(3). Code · tests · registration in hooks/config · smoke-test.

    line 46

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

/integration-gate — IntegrationGate

Trigger: new tool / agent / detector / system / method
Priority: BLOCKING — skipping a Phase = pattern P10 (DP.FM.010)

Checklist (4 steps — strictly in order)

Skipping a Phase → record as an Incident: C2.3.Operations/Incidents/ in your ecosystem-development Repository (if present) or incidents/ governance repo

  1. Promise (Service Clause). What promise does the tool make to the consumer?
    Create or update DP.SC.NNN in PACK-digital-platform/.../08-service-clauses/.
    Contains: trigger · inputs · outputs · response time · invariant · failure mode.
  2. Usage scenarios. Who triggers it? When? Why? In what context? What do they do with the result?
    Minimum 3 scenarios with different consumers. Attach to the Service Clause.
  3. Role. What Role does the tool play in the system?
    Create or update DP.ROLE.NNN in PACK-digital-platform/.../02-domain-entities/.
    Contains: responsibilities · authority · relationships · inputs/outputs as Artifacts.
    Identify the Kind and the Owner Role (who owns it in the Supersystem). Template: DP.D.033.
  4. Implementation. Only after steps (1)–(3).
    Code · tests · registration in hooks/config · smoke-test.
    Implementation header: # see DP.SC.NNN, DP.ROLE.NNN

Exceptions (IntegrationGate is NOT required)

  • Editing an existing tool without changing its promise.
  • Bugfix without changing externally visible behavior.
  • Refactoring (renaming, reorganization) without functional changes.
  • Experimental Script for a single run (if run again — it is already a tool).
<!-- USER-SPACE --><!-- /USER-SPACE -->

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