agentleFS
Kastalien-ResearchKastalien-Research/thoughtbox/.agents/skills/assumptions/SKILL.md

assumptions

Skill64 starsChanged 5 months agoMITView on GitHub

Manage the assumption registry — track, verify, and query assumptions about external dependencies and system behavior. Prevents costly rediscovery of known failures.

4 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

8 rules. 0 are common, 3 are distinctive, and 5 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

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

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

    Read all .assumptions/*.jsonl files

    line 16
  2. Very specific:

    Create a new assumption record in .assumptions/registry.jsonl:

    line 24
  3. Distinctive:

    Read the assumption record by ID

    line 44
  4. Very specific:

    Update last_verified timestamp and confidence score

    line 46
  5. Very specific:

    If verification fails, add to failure_history and reduce confidence

    line 47
  6. Very specific:

    If confidence drops below 0.3, mark status as suspect and warn

    line 48
  7. Distinctive:

    Read all assumption records

    line 51
  8. Distinctive:

    Always end with a summary:

    line 88

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

Manage assumptions: $ARGUMENTS

Commands

Parse the first word of $ARGUMENTS to determine the command:

list — Show all tracked assumptions

  1. Read all .assumptions/*.jsonl files
  2. Parse each line as a JSON record
  3. Display sorted by confidence (lowest first) or staleness (oldest verification first)
  4. Format as a table: ID | Category | Claim | Confidence | Last Verified | Status

add — Register a new assumption

Parse remaining arguments for: --category, --claim, --evidence, --source

Create a new assumption record in .assumptions/registry.jsonl:

{
  "id": "<category>-<short-slug>",
  "category": "<api|dependency|behavior|environment|tooling>",
  "claim": "<what we assume to be true>",
  "evidence": "<what supports this assumption>",
  "source": "<where this was discovered>",
  "confidence": 0.8,
  "created": "<ISO 8601>",
  "last_verified": "<ISO 8601>",
  "verification_method": "<how to test this>",
  "failure_history": [],
  "status": "active",
  "blast_radius": "<what breaks if this assumption is wrong>"
}

verify — Re-verify an assumption

  1. Read the assumption record by ID
  2. Execute the verification method (may involve web search, API calls, or code checks)
  3. Update last_verified timestamp and confidence score
  4. If verification fails, add to failure_history and reduce confidence
  5. If confidence drops below 0.3, mark status as suspect and warn

stale — Show assumptions that need re-verification

  1. Read all assumption records
  2. Filter to those where last_verified is more than 14 days ago
  3. Sort by blast_radius (highest first)
  4. Display with suggested verification actions

seed — Seed registry from MEMORY.md gotchas

  1. Read MEMORY.md
  2. Extract entries from "Gotchas", "Known Bugs", and "MCP Knowledge API Gotchas" sections
  3. For each entry, create an assumption record with:
    • category: inferred from content (api, dependency, behavior, etc.)
    • claim: the gotcha statement
    • evidence: "Discovered empirically" + date from MEMORY.md
    • confidence: 0.9 (verified by experience)
    • verification_method: suggested test

Schema

Each assumption record:

FieldTypeRequiredDescription
idstringyesUnique identifier (category-slug format)
categoryenumyesapi, dependency, behavior, environment, tooling
claimstringyesWhat we assume to be true
evidencestringyesWhat supports this claim
sourcestringyesWhere this was discovered (session, test, docs)
confidencefloatyes0.0 to 1.0 confidence score
createdstringyesISO 8601 creation timestamp
last_verifiedstringyesISO 8601 last verification timestamp
verification_methodstringnoHow to re-test this assumption
failure_historyarraynoPast verification failures with timestamps and details
statusenumyesactive, suspect, retired, verified
blast_radiusstringnoWhat breaks if this assumption is wrong
dependenciesarraynoOther assumptions this depends on

Output

Always end with a summary:

## Assumption Registry Status

Total: {N} assumptions
Active: {N} | Suspect: {N} | Retired: {N}
Stale (>14 days): {N}
Highest blast radius unverified: {assumption_id}

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.