decision-map
Skill1 starsChanged 3 months agoNo licenceView on GitHub
Create, update, or resume a durable multi-session map of unresolved decisions and their dependencies. Use when the user clearly asks for a decision map, wants to track an open decision frontier across sessions, or wants to resume decision work by ticket. Do not use for ordinary implementation planning, one-session design comparison, progress summaries, handoff or checkpoint state, or direct execution of settled decisions.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- SethGammon/Citadeltheir own version, first seen Nov 4, 2026
- Mathews-Tom/armorytheir own version, first seen Nov 1, 2026
- mayankjain1815-commits/CITADELtheir own version, first seen Oct 13, 2026
- timharris707/skillstheir own version, first seen Sep 5, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- SethGammon/Citadel★ 927same name
- Mathews-Tom/armory★ 340same name
- timharris707/skills★ 44same name
- mayankjain1815-commits/CITADEL★ 4same name
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 repository22 other files it gives its agents.
- agent-workflowSkill
- browser-testing-with-devtoolsSkill
- ci-cd-and-automationSkill
- context-engineeringSkill
- debug-systematicallySkill
- design-codebaseSkill
- finish-branchSkill
- frontend-ui-engineeringSkill
- idea-refineSkill
- interview-meSkill
- issue-workflowSkill
- markdown-memorySkill
- memory-handoffSkill
- observability-and-instrumentationSkill
- performance-optimizationSkill
- plan-workSkill
- reliability-checkSkill
- review-and-finishSkill
- security-and-hardeningSkill
- shipping-and-launchSkill
- skill-refactorerSkill
- test-strategySkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
33 rules. 0 are common, 29 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
29
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“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.
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.