Loading...
Loading...
Found 53 Skills
Assess organizational capabilities using radar charts. Use for competitive analysis, gap identification, and strategic planning.
/cs:office-hours <topic> — YC-style 6-question founder interrogation before any advice. Forces clarity on problem, customer, distribution, defensibility, capital, and founder fit.
Use when designing, executing, or facilitating a complete SWOT strategic analysis workflow — especially when the task involves environment scanning (PEST/industry analysis), competitive positioning, S/W/O/T identification and validation, strategy formulation via SO/ST/WO/WT collision, and strategy selection. Trigger on requests such as SWOT analysis, strengths and weaknesses analysis, opportunities and threats analysis, strategy positioning, external environment analysis, competitive strategy, TOWS Matrix, SWOT to strategy, PEST analysis, or any combination of competitive analysis and strategy direction. Also trigger when the user uploads a case, company description, or product brief and asks for strategic analysis or positioning.
Frameworks from Kim & Mauborgne for creating uncontested market space and making competition irrelevant. Use when reframing competitive strategy, escaping commoditization, designing a new category, or applying Strategy Canvas, ERRC, Six Paths, Three Tiers of Noncustomers, Buyer Utility Map, or Strategic Sequence. Includes selection-bias caveats and inline decline notes for iconic cases that later collapsed.
Facilitates the second step of a proven ideal-customer (ICP) method: distilling raw company observations into the few deep-truth attributes that matter, then classifying each as a strength, a weakness, or deliberately both. Takes an observations list (O1, O2, … — file or pasted), proposes attributes one at a time with their supporting observations, kills generic ones with the Opposite Test ('we love our customers' dies), classifies each with a concrete rubric (a third of the market sees it that way, or some customers buy/refuse for it alone), and records the result in STRENGTHS-WEAKNESSES.md (S1, S2, … / W1, W2, …). Load when the user has raw observations and wants to distill them, asks 'what are our real strengths and weaknesses,' or wants to classify what they learned from the honest-look exercise. Do NOT load to gather the raw observations (the previous step), to derive keystones or deal-breakers from classified attributes (later steps), or for a person's individual strengths and weaknesses.