What is the primary purpose of the Prescriptive Strategic Guidance skill?

It is designed to provide directional advice, recommendations, and trade-off analysis when a user asks 'what should I do' regarding a specific technical or project goal.

How does this differ from a planning or roadmap skill?

While a planning skill creates a timeline, this skill focuses on the strategic choice itself, explaining why one approach is better than another and what the trade-offs are.

When should I avoid using this skill?

Do not use it if you need a detailed step-by-step checklist, a specific timeline/roadmap, or success criteria/testing plans, as those are handled by other specialized skills.

Does this skill provide actual code for the solution?

It provides high-level directional steps and principles; it is intended for strategy and architectural decisions rather than generating exhaustive implementation code.

Prescriptive Strategic Guidance

Name: Prescriptive Strategic Guidance
Author: BellaBe

byBellaBe

•

Productivity & Workflow

Provides structured recommendations and strategic direction for complex technical decision-making and project approaches.

About

The Prescriptive Strategic Guidance skill transforms Claude into a high-level advisor for developers and founders, offering structured frameworks for when the path forward is unclear. Instead of just writing code, this skill helps users weigh alternatives, identify trade-offs between speed, cost, and complexity, and select the most effective architectural or operational approach. It is ideal for the 'What should I do?' moments in software development, ensuring that decisions are backed by logic, clear assumptions, and prioritized next steps.

Key Features

Detailed trade-off analysis covering cost, time, risk, and complexity
Immediate next-action prioritization to kickstart implementation
Structured 'Recommended Approach' frameworks with high-level principles
Clear identification of underlying assumptions and major project risks
11 GitHub stars
Explicit A/B alternative comparisons for objective decision making

Use Cases

Evaluating the high-level approach for solving specific technical bottlenecks
Determining the best refactoring strategy for complex legacy codebases
Choosing between different architectural patterns or technology stacks

About

Key Features

Detailed trade-off analysis covering cost, time, risk, and complexity
Immediate next-action prioritization to kickstart implementation
Structured 'Recommended Approach' frameworks with high-level principles
Clear identification of underlying assumptions and major project risks
11 GitHub stars
Explicit A/B alternative comparisons for objective decision making

Use Cases

Evaluating the high-level approach for solving specific technical bottlenecks
Determining the best refactoring strategy for complex legacy codebases
Choosing between different architectural patterns or technology stacks