decision-mapping

Map broad ideas into structured investigation tickets for research, prototyping, and discussion.

Updated Jul 2, 2026
One-click install
npx skills add https://github.com/nseluga/os --skill decision-mapping-nseluga
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: decision-mapping
Source: https://github.com/nseluga/os/tree/main/skills/decision-mapping
Command: npx skills add https://github.com/nseluga/os --skill decision-mapping-nseluga

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill aids in transforming a broad idea into a systematic plan by guiding the user through a sequence of investigation tickets, ensuring each decision is addressed methodically.

Core Features & Use Cases

  • Ticket-Based Decision Making: Organizes a plan into individual investigation tickets, each linked to others and driven to resolution.
  • Stateful Mapping: Maintains a compact Markdown file as the central decision map, updated and referenced throughout the process.
  • Ticket Types: Supports different ticket types for research, prototyping, and discussion-based tasks.
  • Use Case: Ideal for project planning where multiple decisions need to be made over several sessions, ensuring all aspects are thoroughly explored and documented.

Quick Start

Start the decision-mapping skill with a broad idea and follow the structured process to create a decision map and begin resolving tickets.

Frequently Asked Questions about decision-mapping

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

FAQPage Schema
How do I structure project planning decisions across multiple sessions?

Map a broad idea into a structured sequence of investigation tickets to systematically navigate multi-session decision-making processes. Each ticket addresses research, prototyping, or discussion tasks, driving decisions to resolution through a compact Markdown decision map.

What is the best way to track an investigation process from a broad idea to resolution?

Track an investigation process by creating ticket-based decision tasks linked together in a stateful Markdown file. This method organizes research, prototyping, and discussion tickets into a central map that is updated and referenced until every decision reaches resolution.

Can I maintain a structured workflow for project planning without external ticketing system dependencies?

Yes, you can maintain a structured workflow without external dependencies by using a compact Markdown file as your central decision map. The system independently organizes investigation tickets for research and prototyping directly within your local environment.

What ticket types are supported for structured decision-making?

Supported ticket types for structured decision-making include research, prototyping, and discussion-based tasks. Each ticket type is designed to thoroughly explore and document specific aspects of project planning within the overall decision map.

When should I use a ticketing system for decision-making instead of standard project planning?

Use a ticketing system for decision-making when multiple complex decisions need to be made over several sessions. It is ideal for strategic thinking where all aspects of an idea must be thoroughly explored, linked, and documented before resolution.