name: osterwalder-canvas-architect description: "Osterwalder Business Model Canvas Architect workflow skill. Use this skill when the user needs Iterative consultant agent for building and validating logically consistent 9-block Business Model Canvases and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off." version: "0.0.1" category: frontend tags: ["business-model", "osterwalder", "strategy", "bmc", "osterwalder-canvas-architect", "iterative", "consultant", "for"] complexity: beginner risk: safe tools: ["cursor", "codex-cli", "claude-code", "gemini-cli", "opencode"] source: community author: "justmiroslav" date_added: "2026-04-25" date_updated: "2026-04-25"

Osterwalder Business Model Canvas Architect

Overview

This public intake copy packages plugins/antigravity-awesome-skills-claude/skills/osterwalder-canvas-architect from https://github.com/sickn33/antigravity-awesome-skills into the native Omni Skills editorial shape without hiding its origin.

Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.

This intake keeps the copied upstream files intact and uses the external_source block in metadata.json plus ORIGIN.md as the provenance anchor for review.

Osterwalder Business Model Canvas Architect

Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: How It Works, Limitations.

When to Use This Skill

Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.

• Use when designing a new business architecture from scratch.
• Use to audit an existing business for revenue-cost alignment and value delivery gaps.
• Use when a pivot is required and the core business logic needs re-validation.
• Use when the request clearly matches the imported source intent: Iterative consultant agent for building and validating logically consistent 9-block Business Model Canvases.
• Use when the operator should preserve upstream workflow detail instead of rewriting the process from scratch.
• Use when provenance needs to stay visible in the answer, PR, or review packet.

Operating Table

Workflow

This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.

1. Confirm the user goal, the scope of the imported workflow, and whether this skill is still the right router for the task.
2. Read the overview and provenance files before loading any copied upstream support files.
3. Load only the references, examples, prompts, or scripts that materially change the outcome for the current request.
4. Execute the upstream workflow while keeping provenance and source boundaries explicit in the working notes.
5. Validate the result against the upstream expectations and the evidence you can point to in the copied files.
6. Escalate or hand off to a related skill when the work moves out of this imported workflow's center of gravity.
7. Before merge or closure, record what was used, what changed, and what the reviewer still needs to verify.

Imported Workflow Notes

Imported: Overview

A specialized architectural tool for designing and auditing business models using Alexander Osterwalder’s 9-block framework. It focuses on the internal logical "lock" between value propositions, customer segments, and cost structures.

Imported: How It Works

Step 1: Core Value Proposition & Customer Lock

The agent iteratively defines the Value Proposition and Customer Segments to ensure they are logically aligned.

Step 2: Structural Design

The agent builds out the Channels, Relationships, Key Activities, Resources, and Partners.

Step 3: Financial & Consistency Check

Final validation to ensure every activity is accounted for in the Cost Structure and revenue streams align with customer segments.

Examples

Example 1: Ask for the upstream workflow directly

Use @osterwalder-canvas-architect to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.

Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.

Example 2: Ask for a provenance-grounded review

Review @osterwalder-canvas-architect against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.

Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.

Example 3: Narrow the copied support files before execution

Use @osterwalder-canvas-architect for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.

Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.

Example 4: Build a reviewer packet

Review @osterwalder-canvas-architect using the copied upstream files plus provenance, then summarize any gaps before merge.

Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.

Imported Usage Notes

Imported: Examples

Example 1: Subscription-based SaaS (Runnable)

"Draft a Business Model Canvas for an AI-powered agri-tech platform that provides soil analysis for large-scale farmers on a subscription basis. Focus on how the Key Resources (IoT/AI) drive the Cost Structure."

Example 2: Premium Retail Pivot

"Analyze the consistency of a direct-to-consumer organic dairy brand. Ensure the 'Premium Identity' value proposition aligns with the high-touch marketing activities and cost structure."

Best Practices

Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.

• ✅ Prioritize the Value Proposition / Customer Segment lock before filling other blocks.
• ✅ Ensure every "Key Activity" has a corresponding entry in the "Cost Structure".
• ❌ Avoid filling all 9 blocks in one turn; use an iterative approach to maintain logical depth.
• Keep the imported skill grounded in the upstream repository; do not invent steps that the source material cannot support.
• Prefer the smallest useful set of support files so the workflow stays auditable and fast to review.
• Keep provenance, source commit, and imported file paths visible in notes and PR descriptions.
• Point directly at the copied upstream files that justify the workflow instead of relying on generic review boilerplate.

Imported Operating Notes

Imported: Best Practices

• ✅ Prioritize the Value Proposition / Customer Segment lock before filling other blocks.
• ✅ Ensure every "Key Activity" has a corresponding entry in the "Cost Structure".
• ❌ Avoid filling all 9 blocks in one turn; use an iterative approach to maintain logical depth.

Troubleshooting

Problem: The operator skipped the imported context and answered too generically

Symptoms: The result ignores the upstream workflow in plugins/antigravity-awesome-skills-claude/skills/osterwalder-canvas-architect, fails to mention provenance, or does not use any copied source files at all. Solution: Re-open metadata.json, ORIGIN.md, and the most relevant copied upstream files. Check the external_source block first, then restate the provenance before continuing.

Problem: The imported workflow feels incomplete during review

Symptoms: Reviewers can see the generated SKILL.md, but they cannot quickly tell which references, examples, or scripts matter for the current task. Solution: Point at the exact copied references, examples, scripts, or assets that justify the path you took. If the gap is still real, record it in the PR instead of hiding it.

Problem: The task drifted into a different specialization

Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better. Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.

Related Skills

• @00-andruia-consultant - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @00-andruia-consultant-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @10-andruia-skill-smith - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @10-andruia-skill-smith-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.

Additional Resources

Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.

Imported Reference Notes

Imported: Limitations

• Advisory Only: This tool facilitates structural drafting but does not validate market demand or the actual financial viability of the model.
• Execution-Blind: The consistency check is purely logical and cannot predict operational execution bottlenecks.
• Out-of-Scope: This skill does not provide detailed financial forecasting (P&L) or specific legal entity structuring.