agentleFS
UwayxtUwayxt/agent-skills/.agents/skills/business-model-reading/SKILL.md

business-model-reading

Skill4 starsChanged 3 months agoMITView on GitHub

Translate a Business Model Canvas into product modules. Use when bridging business strategy to product architecture.

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:

    The business model dictates the system architecture: If the product doesn't manifest the business's revenue and operational structure, it's …

    line 8
  2. Distinctive:

    Every revenue stream and key activity has a corresponding software module.

    line 24

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

The business model dictates the system architecture. If the product doesn't manifest the business's revenue and operational structure, it's a vanity project.

1. Parse the Business Model Canvas (BMC)

Extract the core value propositions, customer segments, channels, and revenue streams.

2. Derive functional modules

Map every BMC component to a distinct software module. Use a derivation table: | BMC Element | Derived Module | Purpose | Revenue / Cost Impact |

3. Map modules to dashboard structure

Feed the module table into dashboard-scaffolding-contract to design a shell that accommodates all derived modules. Use module-registry-sync manifest schema for each module.

4. Identify growth trajectory

Which modules are MVP (build now) vs expansion (build later)? This feeds directly into mvp-scoping.

Completion criteria

  • Every revenue stream and key activity has a corresponding software module.
  • MVP vs expansion modules are clearly separated.
  • Dashboard shell integration is mapped.

Output format

Produce a business_to_module_map.md artifact containing the derivation table and growth trajectory.

Next Steps

Module table feeds → mvp-scoping (which modules first), dashboard-scaffolding-contract (dashboard shell design), module-registry-sync (manifest per module).

Anti-patterns

  • Inventing modules that don't trace to any revenue stream or operational process.
  • Treating the BMC as a one-time exercise — it should be revisited when the business model pivots.
  • Creating monolithic architectures that cannot isolate revenue-generating modules.

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.