speckit-aee-trace
Skill3 starsChanged 27 days agoMITView on GitHub
Render claim dependencies and inspect epistemic provenance
1 other project uses a version of this.
Adopted by
Most recently taken up by
- electrohire/spec-kit-aeeword for word, first seen Nov 8, 2026
Other versions1 project uses a version of this.
Word for word · 1
- electrohire/spec-kit-aee★ 4100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository24 other files it gives its agents.
- speckit-aee-assessSkill
- speckit-aee-challengeSkill
- speckit-aee-draft-claimsSkill
- speckit-aee-gapsSkill
- speckit-aee-gateSkill
- speckit-aee-report-savingsSkill
- speckit-aee-reviewSkill
- speckit-aee-route-evidenceSkill
- speckit-aee-verifySkill
- speckit-analyzeSkill
- speckit-checklistSkill
- speckit-clarifySkill
- speckit-constitutionSkill
- speckit-convergeSkill
- speckit-evaluator-composeSkill
- speckit-evaluator-reportSkill
- speckit-evaluator-routeSkill
- speckit-evaluator-runSkill
- speckit-implementSkill
- speckit-planSkill
- speckit-specifySkill
- speckit-tasksSkill
- speckit-taskstoissuesSkill
- evaluator-contractSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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
- Distinctive: line 28
Read the generated Mermaid file and report roots, leaves, missing references, cycles, contradictions, and claims capped by weak …
≈ “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.
Files
Aee Trace Skill
AEE Trace
Render the declared dependency/conflict structure for explicit claims. Manually inspect whether evidence and provenance references resolve; graph generation does not fetch or validate those references.
User input
$ARGUMENTSResolve artifact=<path>, apply the project-root and symlink guardrails from /speckit-aee-assess, then run:
python .specify/extensions/aee/scripts/python/run_aee.py graph --input "<artifact>"Read the generated Mermaid file and report roots, leaves, missing references, cycles, contradictions, and claims capped by weak dependencies. The graph expresses declared epistemic structure; it does not establish causality.
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
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.