How does this differ from a planning skill?

While planning skills focus on roadmaps and timelines, the Prescriptive Action skill focuses on directional guidance, trade-offs, and comparing different approaches.

Can this skill help with technical debt?

Yes, it is ideal for evaluating technical debt by outlining the risks and trade-offs of various remediation strategies.

When should I use the Prescriptive Action skill?

Use this skill when you need high-level advice, recommendations, or are asking 'what should I do next' rather than looking for a detailed execution timeline.

What is included in the output of this skill?

The output includes a clear goal statement, a primary recommended approach, alternative options, explicit trade-offs, key risks, and 2-5 immediate next actions.

Prescriptive Decision Advisor

Name: Prescriptive Decision Advisor
Author: BellaBe

byBellaBe

Productivity & Workflow

Provides high-level strategic recommendations and actionable guidance for complex problem-solving and decision-making.

About

The Prescriptive Action skill transforms Claude into a strategic consultant, offering directional advice and prioritized next steps when users encounter technical roadblocks or complex decisions. By focusing on recommended approaches and meaningful alternatives, this skill helps users navigate challenges with clear visibility into trade-offs, risks, and assumptions. It is particularly useful during the early stages of problem-solving, allowing users to align on a direction before moving into detailed roadmaps or procedural execution.

Key Features

0 GitHub stars
Proposes meaningful alternatives with specific 'when to use' criteria
Prescribes immediate next actions to move from theory to practice
Identifies explicit trade-offs across cost, time, and complexity
Generates prioritized, high-level recommended approaches
Highlights critical project risks to monitor during implementation

Use Cases

Choosing between different architectural patterns or technology stacks
Deciding whether to refactor legacy code or initiate a complete rewrite
Seeking diagnostic guidance on how to approach a recurring performance bottleneck

About

Key Features

0 GitHub stars
Proposes meaningful alternatives with specific 'when to use' criteria
Prescribes immediate next actions to move from theory to practice
Identifies explicit trade-offs across cost, time, and complexity
Generates prioritized, high-level recommended approaches
Highlights critical project risks to monitor during implementation

Use Cases

Choosing between different architectural patterns or technology stacks
Deciding whether to refactor legacy code or initiate a complete rewrite
Seeking diagnostic guidance on how to approach a recurring performance bottleneck