agentleFS
lglucaslglucas/ai-dev-operating-system/.claude/skills/business-plan-impact-review/SKILL.md

business-plan-impact-review

Skill12 starsChanged 49 days agoMITView on GitHub

Check every Business Plan change for downstream impact before accepting it — price moves projections, ARPU, LTV and positioning; persona moves GTM, UX and MVP scope; stack moves costs, roadmap and risks. Runs at WIZARD stage 2.8 when turning BP v0.0.1 into v0.0.2, and any time the BP is edited after approval. Use when the user says "mudei o preço", "troquei a persona", "cortei o escopo", "e se eu cobrar por assento?", or when `grow-sustainably` / `multi-ai-review` flag a pricing or packaging change.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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 when revising BP v0.0.1 into v0.0.2 after user feedback.

    line 8
  2. Distinctive:

    Every change must be checked for downstream impact.

    line 10

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Business Plan Impact Review Skill

Use when revising BP v0.0.1 into v0.0.2 after user feedback.

Every change must be checked for downstream impact.

Examples: pricing affects projections; persona affects GTM and UX; stack affects costs and architecture; MVP affects roadmap and DoD.

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.