Skill

new-decision

Scaffold a new decision file with the canonical structure — title, context, options, constraints, stakeholders, timeline, open questions — ready to feed to /decision:analyze. Use this when the user describes a decision verbally rather than handing over an existing decision file.

npx claudepluginhub danielrosehill/claude-code-plugins --plugin decision-evaluation-framework

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Creates a structured decision document the framework analyses can operate on.

SKILL.md

Similar Skills

ui-ux-pro-max

72.7k

Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.

ui-ux-pro-max

context7-mcp

51.8k

Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.

context7-plugin

seo-cannibalization-detector

36.5k

Analyzes multiple pages for keyword overlap, SEO cannibalization risks, and content duplication. Suggests differentiation, consolidation, and resolution strategies when reviewing similar content.

antigravity-bundle-seo-specialist

Stats

Stars0

Forks0

Last CommitApr 28, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

new-decision

New Decision

Creates a structured decision document the framework analyses can operate on.

Procedure

Resolve output location. From $DATA_ROOT/config.json, read outputs.mode and outputs.local_root (or outputs.repo_path). The decision file goes to <root>/queue/<YYYY-MM-DD>-<slug>.md until it's processed (then analyze will move it into a workspace).

If the queue directory doesn't exist, create it.

Interview the user. Walk through:

Title — short, decision-shaped ("Switch payments processor", "Take the contract role").
Context — what's the situation, why is this decision live now?
Options — list 2-5 concrete options. Reject "do something or don't" framings — push for at least 3 distinct paths.
Constraints — hard requirements (budget, timeline, ethical, contractual, capacity).
Stakeholders — who's affected, who has influence, who has veto.
Timeline — when does this need to be decided? When do consequences land?
Open questions — what's still unknown that the user wishes they knew.

Ask one section at a time. Don't fire all six questions at once.

Write the decision file:

# Decision: <Title>

**Date drafted:** <DD/MM/YY>

## Context
...

## Options
1. **<Option A name>** — <one-line>. <expanded>.
2. **<Option B name>** — ...
3. **<Option C name>** — ...

## Constraints
- ...

## Stakeholders
- ...

## Timeline
- Decision deadline: ...
- Consequences land: ...

## Open questions
- ...

Confirm the file path and offer to immediately run /decision:analyze <path>.

Notes

A decision file with fewer than 2 options can still be analyzed (e.g., "should I do X or not"), but flag this — many frameworks degrade when there's no comparator.

Keep options balanced in detail. If one option has a paragraph and the others have a sentence, the analysis will be biased.

New Decision

Creates a structured decision document the framework analyses can operate on.

Procedure

Resolve output location. From $DATA_ROOT/config.json, read outputs.mode and outputs.local_root (or outputs.repo_path). The decision file goes to <root>/queue/<YYYY-MM-DD>-<slug>.md until it's processed (then analyze will move it into a workspace).

If the queue directory doesn't exist, create it.
Interview the user. Walk through:
- Title — short, decision-shaped ("Switch payments processor", "Take the contract role").
- Context — what's the situation, why is this decision live now?
- Options — list 2-5 concrete options. Reject "do something or don't" framings — push for at least 3 distinct paths.
- Constraints — hard requirements (budget, timeline, ethical, contractual, capacity).
- Stakeholders — who's affected, who has influence, who has veto.
- Timeline — when does this need to be decided? When do consequences land?
- Open questions — what's still unknown that the user wishes they knew.
Ask one section at a time. Don't fire all six questions at once.

Write the decision file:

# Decision: <Title>

**Date drafted:** <DD/MM/YY>

## Context
...

## Options
1. **<Option A name>** — <one-line>. <expanded>.
2. **<Option B name>** — ...
3. **<Option C name>** — ...

## Constraints
- ...

## Stakeholders
- ...

## Timeline
- Decision deadline: ...
- Consequences land: ...

## Open questions
- ...

Confirm the file path and offer to immediately run /decision:analyze <path>.

Notes

A decision file with fewer than 2 options can still be analyzed (e.g., "should I do X or not"), but flag this — many frameworks degrade when there's no comparator.
Keep options balanced in detail. If one option has a paragraph and the others have a sentence, the analysis will be biased.