decision-map
Installation
SKILL.md
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.