agentleFS
45ck45ck/business-analysis-skills/.agents/skills/deliverable-consistency-check/SKILL.md

deliverable-consistency-check

Skill28 starsChanged 8 months agoMITView on GitHub

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    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:

    Check consistency across terminology, scope, roles, models, and requirements.

    line 2
  2. Distinctive:

    Look for omissions, contradictions, weak assumptions, and vague language.

    line 16
  3. Distinctive:

    Do not rewrite the whole artifact unless necessary.

    line 30
  4. Distinctive:

    Prefer explainable quality gates.

    line 32

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

Purpose

Check consistency across terminology, scope, roles, models, and requirements.

Use when

  • multiple BA artifacts must agree
  • diagrams and text may have drifted
  • a pack is about to go to review

Inputs

  • artifact or analysis output under review
  • source material and assumptions
  • project context and quality bar

Procedure

  1. Inspect the artifact systematically.
  2. Look for omissions, contradictions, weak assumptions, and vague language.
  3. Distinguish evidence-backed claims from inference.
  4. Record issues by severity.
  5. Recommend targeted fixes, not generic criticism.
  6. Re-state what would make the artifact review-ready.

Outputs

  • inconsistency report
  • terminology fixes
  • traceability mismatches
  • correction checklist

Guardrails

  • Be concrete.
  • Do not rewrite the whole artifact unless necessary.
  • Focus on the highest-leverage defects first.
  • Prefer explainable quality gates.

Completion criteria

  • key defects identified
  • fixes proposed
  • pass/fail or ready/not-ready decision given

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.