agentleFS
Sign inStart free
electrohireelectrohire/spec-kit-aee/.github/skills/speckit-aee-challenge/SKILL.md

speckit-aee-challenge

Skill4 starsChanged 54 days agoMITView on GitHub

Adversarially challenge claims and identify bounded recovery work

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is 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.

  • 1

    Very specific

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

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

    Never delete a conflicting position, manufacture evidence, or accept model self-attestation as independent support.

    line 36

≈ “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

Aee Challenge Skill

AEE Challenge

Challenge explicit claims for observability, atomicity, boundaries, falsifiability, evidence independence, provenance, missing dependencies, cycles, and contradictions.

User input

$ARGUMENTS

Resolve artifact=<path> and optional phase=<phase> using the same prerequisites and path rules as /speckit-aee-assess. Run the AEE adapter's challenge operation, which emits a deterministic failure-mode projection (failures plus bounded recovery proposals) rather than aggregate scoring.

python .specify/extensions/aee/scripts/python/run_aee.py challenge --input "<artifact>" --phase "<phase>"

For every failure in the emitted projection, report:

  • stable failure and claim IDs;
  • the deterministic challenge that triggered;
  • the inspectable breakpoint;
  • evidence references and their kinds;
  • a bounded recovery action and how its completion can be verified.

Never delete a conflicting position, manufacture evidence, or accept model self-attestation as independent support. Recommend rerunning /speckit-aee-assess after recovery work changes the source artifact.

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