Root Cause Investigation
garrytan/gstack
Debugs in four phases (investigate, analyze, hypothesize, implement) under one rule: no fix is made until the root cause is found.
Turn a loose idea into a sequenced map of investigation tickets, then drive them to resolution one at a time.
Apache-2.0Auto-check passed
Install Decision Mapping
$ npx skills add fossasia/eventyay-interpretation --skill decision-mapping -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install fossasia/eventyay-interpretation decision-mapping --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/fossasia/eventyay-interpretation.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/decision-mapping .claude/skills/decision-mapping && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "decision-mapping" agent skill from https://github.com/fossasia/eventyay-interpretation/tree/dev/.agents/skills/decision-mapping into .claude/skills/decision-mapping/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "decision-mapping", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/fossasia/eventyay-interpretation/tree/dev/.agents/skills/decision-mappingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add fossasia/eventyay-interpretation --skill decision-mapping -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install fossasia/eventyay-interpretation decision-mapping --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/fossasia/eventyay-interpretation.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/decision-mapping .agents/skills/decision-mapping && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "decision-mapping" agent skill from https://github.com/fossasia/eventyay-interpretation/tree/dev/.agents/skills/decision-mapping into .agents/skills/decision-mapping/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "decision-mapping", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add fossasia/eventyay-interpretation --skill decision-mapping -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install fossasia/eventyay-interpretation decision-mapping --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/fossasia/eventyay-interpretation.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/decision-mapping .cursor/skills/decision-mapping && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "decision-mapping" agent skill from https://github.com/fossasia/eventyay-interpretation/tree/dev/.agents/skills/decision-mapping into .cursor/skills/decision-mapping/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "decision-mapping", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/fossasia/eventyay-interpretation.git --path .agents/skills/decision-mapping--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add fossasia/eventyay-interpretation --skill decision-mapping -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install fossasia/eventyay-interpretation decision-mapping --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/fossasia/eventyay-interpretation.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/decision-mapping .gemini/skills/decision-mapping && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "decision-mapping" agent skill from https://github.com/fossasia/eventyay-interpretation/tree/dev/.agents/skills/decision-mapping into .gemini/skills/decision-mapping/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "decision-mapping", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install fossasia/eventyay-interpretation decision-mappingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add fossasia/eventyay-interpretation --skill decision-mapping -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/fossasia/eventyay-interpretation.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/decision-mapping .github/skills/decision-mapping && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "decision-mapping" agent skill from https://github.com/fossasia/eventyay-interpretation/tree/dev/.agents/skills/decision-mapping into .github/skills/decision-mapping/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "decision-mapping", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add fossasia/eventyay-interpretation --skill decision-mapping -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install fossasia/eventyay-interpretation decision-mapping --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/fossasia/eventyay-interpretation.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/decision-mapping .opencode/skills/decision-mapping && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "decision-mapping" agent skill from https://github.com/fossasia/eventyay-interpretation/tree/dev/.agents/skills/decision-mapping into .opencode/skills/decision-mapping/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "decision-mapping", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
decision-mapping- GitHub stars
- 1.6k
- Used in
- 1 other repo
- Token cost
- ~927 tokens
- SKILL.md length
- 537 words
- Files
- 1
- Skills in repo
- 38
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Turn a loose idea into a sequenced map of investigation tickets, then drive them to resolution one at a time.
- Works in 3 steps: Run a /grilling + /domain-modeling… → Write a new decision map — mostly fog,… → Stop. Map-building is one session's…
- SKILL.md covers The Decision Map, Ticket Types, Fog of war and Invocation, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Decision Mapping is an agent skill from fossasia/eventyay-interpretation. Turn a loose idea into a sequenced map of investigation tickets, then drive them to resolution one at a time.
Its SKILL.md is about 930 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: A plugin for live interpretation of video streams. The licence is Apache-2.0.
Example prompts
- “/decision-mapping”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Run a /grilling + /domain-modeling session to surface the open decisions. Ask one question at a time.
- Write a new decision map — mostly fog, frontier identified, trivially-decidable entries resolved inline.
- Stop. Map-building is one session's work; do not also resolve tickets.
What it can do on your machine
Read from SKILL.md and the folder at commit 1ca0139. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Decision Mapping loads about 927 tokens when it runs. Until then it costs about 32 tokens; SKILL.md has 537 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from fossasia/eventyay-interpretation at commit 1ca0139, republished under its Apache-2.0 licence (© fossasia). 537 words, ~927 tokens.
Download SKILL.mdSave it as
.claude/skills/decision-mapping/SKILL.md (or your agent's skills folder).- name
- decision-mapping
- description
- Turn a loose idea into a sequenced map of investigation tickets, then drive them to resolution one at a time.
- disable-model-invocation
- true
This skill is invoked when a loose idea requires more than one agent session to turn into a plan. It creates a stateful decision map in a markdown file, and drives the user through a sequence of tickets to resolve the open questions - which may require either prototyping, research or discussion.
The Decision Map
The decision map is a single compact Markdown file, one per planning effort, git-tracked alongside the project. It is the canonical artifact — the whole map is loaded as context into every session, so it must stay compact.
Assets created during tickets should be linked to from the map, not duplicated within it.
Structure
Numbered entries ("tickets"), each its own section keyed by its number:
## #1: Relational Or Non-Relational Database?
Blocked by: #<ticket-number>, #<ticket-number>
Type: Research | Prototype | Grilling
### Question
<question-here>
### Answer
<answer-here>Each ticket must be sized to one 100K token agent session.
Ticket Types
There are three types of tickets:
- Research: Reading documentation, third-party API's, or local resources like knowledge bases. Creates a markdown summary as an asset. Use this when knowledge outside the current working directory is required.
- Prototype: Writing UI or logic code to test a hypothesis, or to explore a design space. Uses the /prototype skill. Creates a prototype as an asset. Use this when "how should it look" or "how should it behave" is the key question.
- Grilling: Conversation with the agent. Uses the /grilling and /domain-modeling skills. Asks one question at a time. The default case.
Fog of war
The map is deliberately incomplete beyond the frontier. Your job is to investigate the frontier, and to resolve tickets in order to push the frontier forward. Push back the fog of war, one node at a time.
At some point, the fog of war should have been pushed back far enough that the path to the finish line is clear. At that point, no more tickets will be required and the decision map can be considered 'done'.
Invocation
There are two ways this skill can be invoked: bootstrap and resume.
Show full SKILL.md (216 more words)Show less
Bootstrap
User invokes with a loose idea.
- Run a /grilling + /domain-modeling session to surface the open decisions. Ask one question at a time.
- Write a new decision map — mostly fog, frontier identified, trivially-decidable entries resolved inline.
- Stop. Map-building is one session's work; do not also resolve tickets.
Resume
User invokes with a path to an existing map and a ticket number.
- Load the whole map as context.
- Run a session to resolve the ticket, invoking skills as needed. If in doubt, use
/grillingand/domain-modeling. - Record what the session resolved in the ticket's body.
- Add newly-discovered tickets (with correct
blocked_byedges). - Stop.
If the decisions made invalidate other parts of the map, update or delete those nodes.
Parallelism
The user may choose to run tickets in parallel, so expect other agents to make changes to the map.
Skipping The Decision Map
Many times, the initial grilling will result in no fog of war. No unresolved tickets. Nothing to do, except implement.
In those situations, you should offer the user the chance to skip the decision map - since the decision map is only needed if multi-session decisions need to be made.
If they skip it, you should recommend either implementing directly or using /to-prd to schedule a multi-session implementation.
© fossasia, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/decision-mapping of fossasia/eventyay-interpretation.
Open the folder on GitHubat commit 1ca0139
Used in 2 other repositories
We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in fossasia/eventyay-interpretation, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Decision Mapping next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Decision Mapping this skillfossasia/eventyay-interpretation | 1.6k | 1 repos | ~927 | Automated safety check: Pass | Apache-2.0 | |
| Root Cause Investigationgarrytan/gstack | 136k | — | ~12k | Automated safety check: Notes | MIT | |
| Idea Ossickn33/agentic-awesome-skills | 47k | 1 repos | ~1.5k | Automated safety check: Pass | MIT | |
| Osint Investigationaffaan-m/ECC | 276k | — | ~5.7k | Automated safety check: Pass | CC-BY-SA-4.0 | |
| Token Mapnexu-io/open-design | 100k | — | ~1.4k | Automated safety check: Pass | Apache-2.0 | |
| Maps Geographyasgeirtj/system_prompts_leaks | 69k | — | ~717 | Automated safety check: Pass | CC0-1.0 |
Similar skills
Idea Os
sickn33/agentic-awesome-skills
Five-phase pipeline (triage → clarify → research → PRD → plan) that turns a raw idea into four linked files: clarifying questions, deep research, a PRD with non-goals and metrics, and a phased…
Osint Investigation
affaan-m/ECC
Sparse-clue OSINT investigation methodology for extracting overlooked leads, connecting fragmented evidence, and testing explanations across sources.
Token Map
nexu-io/open-design
Map an extracted Figma / source-code token bag onto the active OD design system, producing a deterministic mapping the generate stage can consume.
Maps Geography
asgeirtj/system_prompts_leaks
Accurate maps from real geo data — use for any map, or whenever geography would make a good graphic for a deliverable
To Tickets
vinvcn/mattpocock-skills-zh-CN
把 plan、spec 或当前对话拆成一组 tracer-bullet tickets，每个 ticket 声明 blocking edges，并发布到已配置的 tracker；本地用每 ticket 一个文件中的文本 edge，真实 tracker 用 native blocking links。
More from fossasia/eventyay-interpretation
All 38 skills in this repoGit Guardrails Claude Code
fossasia/eventyay-interpretation
Set up Claude Code hooks to block dangerous git commands (push, reset --hard, clean, branch -D, etc.) before they execute.
Diagnosing Bugs
fossasia/eventyay-interpretation
Diagnosis loop for hard bugs and performance regressions. An agent skill from fossasia/eventyay-interpretation.
Domain Modeling
fossasia/eventyay-interpretation
Build and sharpen a project's domain model. An agent skill from fossasia/eventyay-interpretation.
Improve
fossasia/eventyay-interpretation
Survey any codebase as a senior advisor and produce prioritized, self-contained implementation plans for OTHER models/agents to execute.
Migrate To Shoehorn
fossasia/eventyay-interpretation
Migrate test files from as type assertions to @total-typescript/shoehorn.
Setup Pre Commit
fossasia/eventyay-interpretation
Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo.
Questions about Decision Mapping
What does Decision Mapping do?
Turn a loose idea into a sequenced map of investigation tickets, then drive them to resolution one at a time. Decision Mapping is an agent skill from fossasia/eventyay-interpretation. Turn a loose idea into a sequenced map of investigation tickets, then drive them to resolution one at a time.
How do I install Decision Mapping in Claude Code?
Run `npx skills add fossasia/eventyay-interpretation --skill decision-mapping -a claude-code`. Or copy the skill folder (.agents/skills/decision-mapping in fossasia/eventyay-interpretation) into .claude/skills/decision-mapping in your project. Claude Code loads it when a task matches its description.
How do I install Decision Mapping in Codex?
Run `npx skills add fossasia/eventyay-interpretation --skill decision-mapping -a codex`. Or copy the skill folder (.agents/skills/decision-mapping in fossasia/eventyay-interpretation) into .agents/skills/decision-mapping in your project. Codex loads it when a task matches its description.
Can I use Decision Mapping in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add fossasia/eventyay-interpretation --skill decision-mapping -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/decision-mapping, .gemini/skills/decision-mapping, .github/skills/decision-mapping and .opencode/skills/decision-mapping in your project.
What does Decision Mapping need to run?
SKILL.md names no scripts, command-line tools or credentials: Decision Mapping is instructions for the agent only.
Does Decision Mapping access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Decision Mapping safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Decision Mapping use?
Decision Mapping is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Decision Mapping use?
About 927 tokens (SKILL.md is roughly 3.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Decision Mapping?
Skills that share tags, products or a category with Decision Mapping: Root Cause Investigation (garrytan/gstack, 136k stars), Idea Os (sickn33/agentic-awesome-skills, 47k stars), Osint Investigation (affaan-m/ECC, 276k stars) and Token Map (nexu-io/open-design, 100k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Decision Mapping?
fossasia (a GitHub organization) maintains it in fossasia/eventyay-interpretation, which has 1,551 GitHub stars. The repository holds 38 skills in this directory. The repository was last updated on October 5, 2026.
Source: fossasia/eventyay-interpretation on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.