agentleFS
Sign inStart free
itseffiitseffi/agentic-os/.agents/skills/structured-product-strategy/SKILL.md

structured-product-strategy

Skill114 starsChanged 10 months agoMITView on GitHub

Build a complete product strategy from context, including objective, users, superpowers, vision, pillars, impact, and roadmap.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create a coherent strategy from product context.

    line 8
  2. Distinctive:

    Write a 1-2 sentence objective that is ambitious and achievable.

    line 13
  3. Distinctive:

    Write 2-3 paragraphs linking objective, users, and superpowers.

    line 23
  4. Distinctive:

    Do not prioritize unless asked.

    line 31
  5. Distinctive:

    Use this skill when the task directly matches the workflow described above.

    line 50
  6. Distinctive:

    Do not use this skill when the request is unrelated, low-stakes, or better handled by a simpler direct response.

    line 54

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Structured Product Strategy

Create a coherent strategy from product context.

Instructions

Step 1: Define objective

  • Write a 1-2 sentence objective that is ambitious and achievable.

Step 2: Define users and needs

  • Choose 1-2 core user groups.
  • List 3-4 concrete needs for each.

Step 3: Identify superpowers

  • Name 3-4 unique advantages that can compound.

Step 4: Draft vision

  • Write 2-3 paragraphs linking objective, users, and superpowers.

Step 5: Define pillars and impact

  • Create 2-4 strategy pillars.
  • Explain causal impact mechanism to business outcomes.

Step 6: Draft roadmap by pillar

  • Provide 3-10 initiatives per pillar.
  • Do not prioritize unless asked.

Output

  • Objective
  • Users
  • Superpowers
  • Vision
  • Pillars
  • Impact mechanism
  • Roadmap by pillar

Quality Bar

  • Ground every claim in provided context.
  • State assumptions explicitly when context is missing.

When to Use

Use this skill when the task directly matches the workflow described above.

When Not to Use

Do not use this skill when the request is unrelated, low-stakes, or better handled by a simpler direct response.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free