agentleFS
Sign inStart free
itseffiitseffi/agentic-os/.agents/skills/limit-based-strategy/SKILL.md

limit-based-strategy

Skill114 starsChanged 10 months agoMITView on GitHub

Develop a limit-based product strategy with convergence milestones, acceleration levers, assumptions, and phased execution.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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:

    Use limit-based thinking to move from problem statement to execution plan.

    line 8
  2. Distinctive:

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

    line 47
  3. Distinctive:

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

    line 51

≈ “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

Limit-Based Strategy

Use limit-based thinking to move from problem statement to execution plan.

Instructions

Step 1: Define growth variable and limit state

  • Identify the primary growth variable.
  • Describe the mature limit state clearly.

Step 2: Identify core properties

  • List features and dynamics that must exist at the limit.

Step 3: Estimate convergence

  • Provide milestones at 10%, 25%, 50%, 75%, and 90% with dates/triggers.

Step 4: Identify acceleration levers

  • List levers to steepen convergence.
  • Prioritize top 1-2 highest impact levers.

Step 5: List critical assumptions

  • Capture assumptions and how each will be validated.

Step 6: Produce execution design

  • One-sentence vision.
  • Major roadmap milestones.
  • 3-phase plan: Foundation, Acceleration, Optimization.
  • Resource guidance.

Output

  • Growth variable
  • Limit state
  • Core properties
  • Convergence estimate
  • Acceleration strategies
  • Critical assumptions + validation
  • Vision and phased execution

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