decision-mapping

Converts loose ideas into sequenced investigation tickets tracked in a markdown decision map.

1|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/mst-software-vn/mst-checkscam --skill decision-mapping-mst-software-vn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: decision-mapping
Source: https://github.com/mst-software-vn/mst-checkscam/tree/main/.claude/skills/decision-mapping
Command: npx skills add https://github.com/mst-software-vn/mst-checkscam --skill decision-mapping-mst-software-vn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a vague product or architecture idea into an actionable plan often spans multiple agent sessions, and open questions get lost between them. This Skill creates a persistent, git-tracked decision map that captures every unresolved question as a numbered ticket and drives them to resolution one at a time. ## Core Features & Use Cases - Decision Map Creation: Bootstraps a compact markdown file of numbered tickets with blocked-by dependencies, keeping the whole map loadable as context in every session. - Typed Tickets: Classifies each open question as Research, Prototype, or Discuss, and invokes the appropriate supporting skills (/grilling, /domain-modelling, /prototype) to resolve it. - Stateful Resume Workflow: Loads an existing map, resolves one ticket per session, records the answer, and appends newly discovered tickets with correct dependency edges. - Use Case: You have a loose idea like "build a scam-reporting platform" but are unsure about the database choice, auth model, and moderation flow. Bootstrap a decision map, then resolve tickets one session at a time until the path to implementation is clear. ## Quick Start Ask the agent to bootstrap a decision map for your loose idea, or resume an existing map by providing its file path and the ticket number you want to resolve.

Frequently Asked Questions about decision-mapping

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn a vague idea into an actionable plan across multiple sessions?▼

Bootstrap a decision map by running a grilling and domain-modelling session to surface open decisions, then write them as numbered tickets in a markdown file. Resolve tickets one per session until the fog of war is pushed back and implementation is clear.

What is a decision map in agent-based planning?▼

A decision map is a single compact, git-tracked markdown file containing numbered tickets, each with a question, an answer section, a type (Research, Prototype, or Discuss), and blocked-by dependencies. The whole map is loaded as context into every working session.

How do I resume work on an existing decision map?▼

Invoke the skill with the path to the existing map file and a ticket number. The session loads the full map, resolves that ticket using the appropriate skills, records the answer, and adds any newly discovered tickets with correct dependency edges.

When should I skip creating a decision map?▼

Skip the decision map when the initial grilling session reveals no unresolved questions and no fog of war. In that case, implement directly or use a PRD-style skill to schedule a multi-session implementation instead.

Can multiple agents work on decision map tickets in parallel?▼

Yes, tickets can be resolved in parallel by different agents, so the map is designed to tolerate concurrent edits. Each ticket is sized to fit within a single 100K token agent session to keep work isolated.