decision-mapping

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

Updated Aug 5, 2026
One-click install
npx skills add https://github.com/pd-phuc/laravel-template --skill decision-mapping-pd-phuc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: decision-mapping
Source: https://github.com/pd-phuc/laravel-template/tree/main/.claude/skills/decision-mapping
Command: npx skills add https://github.com/pd-phuc/laravel-template --skill decision-mapping-pd-phuc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a vague idea into an actionable plan often requires multiple agent sessions of research, prototyping, and discussion, and without structure those open questions get lost. This Skill creates a persistent, git-tracked decision map that sequences unresolved questions into tickets 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 dependency edges, ticket types (Research, Prototype, Discuss), and a deliberately incomplete frontier. - Ticket Resolution Sessions: Resumes an existing map, loads it fully into context, resolves one ticket per session using supporting skills like grilling, domain-modelling, or prototyping, and records the outcome. - Fog-of-War Planning: Keeps the map minimal beyond the frontier, adding newly discovered tickets with correct blocked-by edges as decisions unfold, and supports parallel agents editing the same map. - Use Case: A developer has a loose idea for a new product feature. The Skill interviews them, writes a decision map with open questions like database choice or UI approach, then resolves each ticket in focused sessions until the path to implementation is clear. ## Quick Start Ask the agent to turn your loose idea into a decision map of investigation tickets, or resume an existing map by providing its path and a ticket number.

Frequently Asked Questions about decision-mapping

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

FAQPage Schema
What is a decision map in multi-session planning?▼

A decision map is a single compact, git-tracked markdown file containing numbered tickets, each with a question, answer, type (Research, Prototype, or Discuss), and blocked-by dependencies. The whole map loads into every session, so it must stay small.

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

Invoke the skill with the path to the existing map and a ticket number. The agent loads the full map, resolves that ticket in one session using research, prototyping, or discussion, records the outcome, and adds any newly discovered tickets.

Can multiple agents work on the same decision map in parallel?▼

Yes, the skill explicitly supports parallel ticket resolution. Users may run tickets concurrently, so agents expect other sessions to modify the shared map and must handle those changes when recording results.

When should I skip creating a decision map?▼

Skip the map when the initial grilling surfaces no unresolved questions and no fog of war remains. In that case the skill recommends implementing directly or using a PRD-based skill to schedule multi-session implementation instead.