decision-map SKILL.md skillA
decision-map from mathews-tom/armory is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add mathews-tom/armory/decision-map@v1.0.1Pins v1.0.1 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- mathews-tom/armory
- Path
skills/decision-map/SKILL.md- Versions recorded
- 2
- Latest version
- v1.0.1, committed Aug 16, 2026
- First version recorded
- Aug 16, 2026
- Size
- 10,961 bytes
- Repository stars
- 334
- License
- MIT
Maps the unresolved architecture, policy, and scope decisions that must be answered before planning can start: one durable decision ticket per question on the issue tracker, typed and blocker-linked under a parent map, with fog-of-war, out-of-scope, a computed frontier, and one decision resolved per invocation. Triggers on: "map the decisions", "what do we need to decide", "identify the unknowns", "not ready to plan yet", "decision map", "chart this effort", "work the next decision ticket…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Decision Map ## Scope and Trigger Boundary Ask one discriminator before creating anything: **Do we know what should be built?** If no, map unresolved decisions. If yes, route known design into milestones with `plan-prompts` or implementation-sized work with `task-decomposer`. A decision map produces decisions and evidence, never implementation deliverables. | Situation | Package | |---|---| | Destination or design still unclear; decisions would have to be invented | `decision-map` | | Design known; needs milestones and execution prompts | `plan-prompts` | | Feature specified; needs implementation slices, tests, risks | `task-decomposer` | | Plan exists; needs a pre-implementation audit | `plan-review` | | Plan approved; needs execution across sessions | `milestone-runner` | | Repo audit needs standalone remediation plans, optionally as issues | `codebase-advisor --issues` | | One decision needs a durable record | `adr-writer` | | Session state must survive a handoff | `handoff` | Do not turn vague hopes into implementation tasks merely to make progress appear orderly. A sharp but currently unanswered question is a ticket. A question that cannot yet be stated sharply is fog. …
Read the whole file at its exact version.
How to install
mdr add mathews-tom/armory/decision-map@sha256:e13b59fd07ce3f1bThe line at the top of this page pins the label v1.0.1, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_2rcwdu7xo7m6faoc)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, all committed on Aug 16, 2026.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.1 latest | 2026-08-16 | b2ce79b | 10,961 B | A | view · diff |
| v1.0.0 | 2026-08-16 | a553142 | 10,811 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (10961 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
mathews-tom/armory · 334 stars · license MIT · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_2rcwdu7xo7m6faoc GET https://markdownregistry.com/api/v1/resolve?ref=mathews-tom/armory/decision-map GET https://markdownregistry.com/api/v1/blob/e13b59fd07ce3f1bfcbf63641b21353d3654603ffb0ff7fdb2c101b63b739bc8
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from mathews-tom/armory
Every file in mathews-tom/armory