# Map Complex Decisions Into Investigation Tickets

Complex planning work often stalls when open decisions mix with implementation tasks. This skill turns uncertainty into compact tickets and guides each session to resolution.

## Install

```bash
npx skillstore add mattpocock/decision-mapping
```

## Metadata

- Status: approved
- Slug: mattpocock-decision-mapping
- Skillstore revision: r1
- Version status: missing
- Tree hash: d5059c04e44b0c747726108287efd897fc1eb82d732c416346ed899fc1fd4d5f
- Author: mattpocock
- GitHub username: mattpocock
- License: MIT
- Repository: https://github.com/mattpocock/skills/tree/main/skills/in-progress/decision-mapping/
- Ref: b8ca75d2c0a7e7102978993058777d82b8ab2610
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 77
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/mattpocock-decision-mapping
- Manifest: https://skillstore.pages.dev/api/skills/mattpocock-decision-mapping/manifest

## Capabilities

- Creates a compact Markdown decision map for one planning effort.
- Structures entries as numbered tickets with dependencies, type, question, and answer.
- Supports bootstrap sessions from loose ideas.
- Supports resume sessions for a specified map path and ticket number.
- Classifies tickets as Research, Prototype, or Grilling.
- Updates the map when decisions reveal new tickets or invalidate old nodes.

## Use Cases

- Plan Ambiguous Product Work: Turn a broad product idea into ordered questions, research tasks, and clear decision points.
- Resolve Architecture Choices: Break architecture uncertainty into research, prototype, and discussion tickets with dependency tracking.
- Coordinate Long Investigations: Maintain a compact map when multiple sessions or agents must push related decisions forward.

## Prompt Templates

### Create a Decision Map

```
Use decision-mapping for this idea: [brief idea]. Ask one question at a time and create the first map.
```

### Resume One Ticket

```
Use decision-mapping with [map path] and ticket #[number]. Load the full map, resolve only this ticket, then update the map.
```

### Map Architecture Decisions

```
Use decision-mapping to map unresolved architecture choices for [project]. Separate research, prototype, and grilling tickets with dependencies.
```

### Coordinate Parallel Investigation

```
Use decision-mapping to review [map path], identify tickets that can run in parallel, and preserve blocked_by dependencies.
```

## Limitations

- Does not resolve tickets during the initial map-building session.
- Depends on other skills for prototyping, grilling, and domain modeling.
- Requires the full decision map to remain compact enough for session context.
- Does not replace user judgment when deciding parallel work order.

## Best Practices

- Keep each ticket small enough for one 100K token session.
- Link assets from the map instead of copying full artifacts into it.
- Resolve tickets in dependency order unless the map clearly supports parallel work.

## Anti Patterns

- Using the map for simple tasks with no unresolved decisions.
- Resolving tickets during the initial bootstrap session.
- Duplicating large research notes inside the decision map.

## Security Audit

- Audited at: 2026-07-06T17:49:33.822\+00:00
- Summary: All four static findings are false positives caused by Markdown fences or inline field names in SKILL.md. No prompt injection, data exfiltration intent, or unauthorized command execution evidence was found.

## Stats

- Views: 0
- Downloads: 5
- Favorites: 0
- Popularity score: 0