strategy-os: Skill for Claude Code

.claude/skills/stg-designing-solutions/SKILL.md

stg-designing-solutions is a skill for Claude Code from LeanOS-Technologies/strategy-os. It costs 42 tokens per session (2,443 once invoked), scanned A, original, MIT.

A solution-planning method that connects customer problems, target buyers, pricing constraints, competitors, and the product’s first version. It also chooses a growth model, such as product-led growth (customers discover and adopt the product themselves), network growth, traditional sales, or a mix.

In plain words
What is it for?
Use it to map features to problems, define MVP scope, choose a growth model, create product positioning, identify the key moment when users understand the product’s value, and design growth loops.
Why use it?
It prevents product ideas from being designed separately from customer needs, costs, and how the business will grow. It makes the proposed positioning and minimum viable product (MVP) traceable to the underlying research.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is LeanOS-Technologies/strategy-os's own configuration. It tells Claude Code how to work on strategy-os itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything strategy-os configures →

Reuse

Borrowing it

Nothing to install: this file belongs to LeanOS-Technologies/strategy-os. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/LeanOS-Technologies/strategy-os/main/.claude/skills/stg-designing-solutions/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/LeanOS-Technologies/strategy-os

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for stg-designing-solutions

README.md
[![agentmods](https://agentmods.dev/badge/skills/leanos-technologies/strategy-os/stg-designing-solutions/github.svg)](https://agentmods.dev/skills/leanos-technologies/strategy-os/stg-designing-solutions)
Your own site
<a href="https://agentmods.dev/skills/leanos-technologies/strategy-os/stg-designing-solutions"><img src="https://agentmods.dev/badge/skills/leanos-technologies/strategy-os/stg-designing-solutions/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for stg-designing-solutions

Your own site · 80×15
<a href="https://agentmods.dev/skills/leanos-technologies/strategy-os/stg-designing-solutions"><img src="https://agentmods.dev/badge/skills/leanos-technologies/strategy-os/stg-designing-solutions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 42 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,443 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00042 $0.02443
Opus 5 $0.00021 $0.01222
Sonnet 5 $0.00008 $0.00489
Haiku 4.5 $0.00004 $0.00244

Measured 9d ago against content hash f689ebcbeb8b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

stg-designing-solutions scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/stg-designing-solutions/SKILL.md · 201 lines

How it starts

The opening of the file, as written. The whole thing — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Solution Design

Design solution architecture: select growth model, assemble positioning, map features to problems, define MVP scope, design growth loops. Output is the Solution Design section of the register -- a derived design artifact constrained by all three hypotheses, not a hypothesis itself.

Procedure

Step 1: Load Hypothesis Context [S]

Read: problem, segment, unit economics hypotheses. Also read competitive analysis (gaps, alternatives) for positioning assembly.

Extract constraints each hypothesis places on the solution:

  • Problem -> what must be solved (top problems by severity)
  • Segment -> buyer type (user=buyer or committee), ACV range, time-to-value expectations
  • Unit Economics -> cost constraints (gross margin target, COGS limits)

Extract positioning inputs:

  • Problem claim -> the problem statement for the positioning template
  • Segment claim -> the target for the positioning template
  • Competitive analysis -> alternatives and gaps for the "unlike" clause
  • Aha moment (assembled in Step 5) -> unique capability clause

Produce: hypothesis constraints table + positioning inputs.

Gate: constraints_extracted: bool -- at least one constraint from each hypothesis documented, positioning inputs identified.

  • Pass: Step 2.
  • Fail: If a hypothesis is missing, note the gap. Proceed with available constraints, flagging reduced confidence.

Step 2: Select Growth Architecture [R]

Score buyer characteristics against decision matrix:

Factor PLG Network Traditional Source
ACV < $5K < $5K > $25K Segment hypothesis
Buyer type User = buyer User = buyer Committee Segment hypothesis
Time-to-value < 1 day < 1 day Weeks+ Product nature
Collaboration Optional Inherent Either Product nature
Shareability Medium High Low Product nature

For ACV between $5K-$25K: Hybrid. Document which factors pulled in which direction.

Read the full file on GitHub · 201 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 9d ago First seen · 201 lines · 42 tokens per session scan A f689ebcbeb8b

Subscribe to this mod's changes

stg-designing-solutions is a skill published in the GitHub repository LeanOS-Technologies/strategy-os (37 stars, last pushed 4mo ago), licensed MIT. It adds 42 tokens to every session and 2,443 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

email-sequence

When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," or "lifecycle…

davila7/claude-code-templates · 84 tokens

llm-app-patterns

Production-ready patterns for building LLM applications. Covers RAG pipelines, agent architectures, prompt IDEs, and LLMOps monitoring. Use when designing AI applications, implementing RAG, building agents, or setting up LLM observability.

davila7/claude-code-templates · 54 tokens

qa-test-planner

Generate comprehensive test plans, manual test cases, regression test suites, and bug reports for QA engineers. Includes Figma MCP integration for design validation.

davila7/claude-code-templates · 34 tokens

guidance

Control LLM output with regex and grammars, guarantee valid JSON/XML/code generation, enforce structured formats, and build multi-step workflows with Guidance - Microsoft Research's constrained generation framework.

davila7/claude-code-templates · 38 tokens

content-research-writer

Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section. Transforms your writing process from solo effort to collaborative partnership.

davila7/claude-code-templates · 49 tokens

training-llms-megatron

Trains large language models (2B-462B parameters) using NVIDIA Megatron-Core with advanced parallelism strategies. Use when training models >1B parameters, need maximum GPU efficiency (47% MFU on H100), or require tensor/pipeline/sequence/context/expert parallelism. Production-ready framework used for Nemotron, LLaMA…

davila7/claude-code-templates · 82 tokens