strategy

Convert unclear requests into structured outputs using decision, ideation, and clarity frameworks.

110|14|Updated May 12, 2026
One-click install
npx skills add https://github.com/EliasOulkadi/shokunin --skill strategy-eliasoulkadi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: strategy
Source: https://github.com/EliasOulkadi/shokunin/tree/main/.pack/skills/strategy
Command: npx skills add https://github.com/EliasOulkadi/shokunin --skill strategy-eliasoulkadi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps users turn fuzzy goals into actionable decisions by providing structured brainstorming (divergent/convergent), prompt diagnosis (7 dimensions), and decision frameworks (scoring and risk checks) that prevent vague, inconsistent outcomes.

Core Features & Use Cases

  • Track-based structured workflow: chooses between Decision, Ideation, and Clarity, running them sequentially when needed (Clarity → Ideation → Decision).
  • Decision frameworks with timeboxing: applies ICE, Impact/Effort matrix, First Principles, and Pre-Mortem with explicit scoring and justification.
  • Prompt engineering via 7-dimension diagnosis: detects weak prompt dimensions (0–3) and rewrites the prompt with a clear changelog and iteration signal.
  • Production-ready strategy artifacts: enforces required output fields (framework rationale, raw output, action with owner/next step/deadline, and one rejected alternative) plus a production checklist.

Quick Start

Run a strategy session for choosing between three architecture options, including scoring, tie-breaking, and a prioritized next action with deadline.

Frequently Asked Questions about strategy

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

FAQPage Schema
What is structured brainstorming and when do I need it for decision making?

Structured brainstorming converts unclear goals into actionable decisions using divergent and convergent tracks. You need it when facing fuzzy ideation sessions or high-stakes selections among alternatives that require explicit frameworks, scoring, and risk checks to prevent vague outcomes.

How do I diagnose and rewrite a weak prompt using a 7-dimension framework?

Prompt diagnosis evaluates weak dimensions on a 0–3 scale and rewrites the prompt with a clear changelog and iteration signal. It works by detecting missing structural elements in prompt engineering workflows, ensuring consistent formatting, examples, and production-ready outputs.

How do I run a structured decision-making session with ICE and Impact/Effort frameworks?

Run a decision session by applying ICE, Impact/Effort matrix, First Principles, and Pre-Mortem frameworks with timeboxing. The workflow enforces explicit scoring, justification, and tie-breaking, concluding with a prioritized action item containing an owner, next step, and deadline.

Can I use timeboxing to prevent endless brainstorming and force a decision?

Timeboxing enforces strict time limits during framework application to prevent endless brainstorming. It works within structured decision-making and ideation tracks by bounding divergent and convergent phases, forcing explicit scoring, and requiring a final action with a rejected alternative.

What is the best way to structure a prompt rewrite workflow for consistent formatting?

The best way to structure a prompt rewrite workflow is applying a 7-dimension diagnosis to detect weak areas, revising with explicit frameworks, and verifying against a production checklist. This ensures consistent formatting, generates a clear changelog, and signals when iteration is needed.

Why does my brainstorming output lack a clear action item and rejected alternative?

Brainstorming output lacks clear actions when missing the production-ready strategy artifact structure. This structure enforces required fields including framework rationale, raw output, an action with owner, next step, deadline, and one explicitly rejected alternative to ensure decision completeness.