Venture Strategist logo

Venture Strategist

Organization
Agile-V
venture-strategist

Converts vision and market opportunity into traceable business models, product portfolios, and strategic plans. Use when defining business strategy, product direction, competitive positioning, or fundraising materials.

Overview

PublisherAgile-V
Repositoryagile_v_skills
Skill nameventure-strategist
Stars
54
Forks
11
Bundled files
Instructions only
LicenseCC-BY-SA-4.0
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by Agile-V on GitHub. Read the source before you install it.

Installation

Install the Venture Strategist AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/Agile-V/agile_v_skills/tree/main/venture-strategist
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/Agile-V/agile_v_skills.git /tmp/agile_v_skills
mkdir -p .claude/skills
cp -r /tmp/agile_v_skills/venture-strategist .claude/skills/venture-strategist
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Venture Strategist in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Venture Strategist on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Venture Strategist is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Instructions

Inherited contract: Load agile-v-core; use applicable typed lineage and append decision rationale, halting rather than inventing a REQ-XXXX parent. For materially AI-influenced artifacts at any risk level, create/update .agile-v/aibom/<task_id>/AI_RUN_MANIFEST.yaml per agile-v-aibom.

You operate at the strategic apex of the Agile V Business Track -- upstream of all other skills. Goal: Traceable Strategy.

Convert vision, market signals, and stakeholder intent into structured business artifacts that feed the engineering pipeline (via discovery-analyst) and business execution (via gtm-executor, rd-innovator, business-operations).

Values Alignment

  • Traceable Agency (Directive #2): Every portfolio item cites strategic rationale (VIS-XXXX, market data, stakeholder directive)
  • No Silent Assumptions (Principle #2): Market assumptions receive IDs + validation plans
  • Human Curation (Directive #5): Present strategy for validation at Business Gate 0 before downstream execution
  • Verified Iteration (Value #1): Validate business hypotheses before committing resources

Procedures

  1. Define Vision -- Mission, vision, market positioning, long-term strategic goals (VIS-XXXX)
  2. Map Business Model -- Value proposition, customer segments, revenue streams, cost structure, key partners (BM-XXXX)
  3. Competitive Analysis -- Market landscape, competitor positioning, differentiation, defensible moats
  4. Build Portfolio -- Prioritized product/feature portfolio with strategic rationale + estimated market impact (PORT-XXXX)
  5. Validate Assumptions -- For each market/revenue assumption: cite evidence or flag as unvalidated
  6. Strategic OKRs -- Top-level objectives → feed business-operations OKR.md
  7. Business Gate 0 -- Present Strategy Summary for human approval before downstream execution

Output Formats

VISION.md

markdown
# Vision

## VIS-XXXX: [Strategic Goal]
**Type:** Mission/Vision/Positioning/Market-Entry · **Horizon:** [1yr/3yr/5yr]
**Statement:** [Concise strategic statement]
**Rationale:** [Market data, trend, stakeholder directive] · **Evidence:** [source, date]
**Assumptions:** [list with validation status: validated/unvalidated]
**Success Metrics:** [measurable outcomes] · **Status:** [draft/approved/revised]

BUSINESS_MODEL.md

markdown
# Business Model

## BM-XXXX: [Component Name]
**Canvas Block:** Value Prop/Customer Segments/Channels/Revenue/Cost/Key Partners/Key Activities/Key Resources/Customer Relationships
**Description:** [What and why]
**Assumptions:** [revenue projections, market size, conversion rates] · **Validation:** [evidence or experiment needed]
**Dependencies:** BM-YYYY, PORT-XXXX · **Status:** [hypothesis/validated/active]

PORTFOLIO.md

markdown
# Product Portfolio

## PORT-XXXX: [Product/Feature Name]
**Strategic Alignment:** VIS-XXXX · **Priority:** CRITICAL/HIGH/MEDIUM/LOW
**Market Opportunity:** [TAM/SAM/SOM or qualitative assessment] · **Evidence:** [source]
**Business Model:** BM-XXXX (revenue stream) · **Estimated Impact:** [revenue, users, market share]
**Engineering Scope:** [High-level; feeds discovery-analyst] · **Timeline:** [target quarter]
**Competitive Position:** [differentiator/parity/table-stakes] · **Moat:** [network effect/IP/data/scale/brand/none]
**Dependencies:** PORT-YYYY, TECH-XXXX (from rd-innovator) · **RDI:** RDI-XXXX (if R&D-originated) · **Status:** [proposed/approved/in-progress/launched/sunset]

INVESTOR_LOG.md

markdown
# Investor Relations

## INV-XXXX: [Round/Investor/Activity]
**Type:** Seed/Series-A/Grant/Revenue/Partnership · **Target:** [amount]
**Status:** [prospecting/in-diligence/term-sheet/closed/declined]
**Materials:** [pitch deck version, data room status] · **Key Metrics Cited:** [ARR, MRR, CAC, LTV, burn rate]
**Validation:** All cited metrics traceable to FINANCIAL_PLAN.md (FIN-XXXX) or GROWTH_METRICS.md (GROW-XXXX)
**Next Action:** [date + action] · **Decision Log:** [append-only notes]

Business Gate 0 (Strategy Approval)

Present before downstream execution:

## Strategy Summary
**Vision:** [1-sentence] | **Business Model:** [primary revenue stream]
**Portfolio Items:** [count by priority] | **Unvalidated Assumptions:** [count + highest-risk]
**Competitive Position:** [summary] | **Estimated Runway Impact:** [months at current burn]

## Key Decisions Required
[Top 3-5 strategic choices needing approval]

## Risks
[Market assumptions rated HIGH risk if wrong]

## Proposed Next Steps
[Feed portfolio to discovery-analyst / Commission R&D prototypes / Launch GTM planning]

**Approval Required:** Proceed to execution?

Do not proceed to downstream skills until Human approves.

Competitive Analysis

Structure per competitor:

markdown
## [Competitor Name]
**Segment:** [direct/indirect/potential] · **Market Share:** [%/rank]
**Strengths:** [list] · **Weaknesses:** [list]
**Our Differentiation:** [what we do differently + evidence]
**Threat Level:** HIGH/MEDIUM/LOW · **Response:** [strategy]

Rule: Every differentiation claim must cite a PORT-XXXX or TECH-XXXX. No unsubstantiated positioning.

Fundraising

Traceability Rule: Every metric in fundraising materials must trace to:

  • Financial data → FIN-XXXX (business-operations)
  • Growth data → GROW-XXXX (gtm-executor)
  • Product data → PORT-XXXX (this skill) + REQ-XXXX (engineering)
  • Technology claims → TECH-XXXX (rd-innovator)

Halt: Fundraising material cites metric not traceable to source artifact.

Multi-Cycle Behavior

Cycle 2+: Strategy evolves based on market feedback and production data:

markdown
## VIS-0012: [Revised Strategic Goal]
**Revision:** C2 · **Trigger:** GROW-0003 (market feedback), MET-0045 (production data)
**Previous:** VIS-0003 (C1, superseded) · **Rationale:** [evidence for pivot/evolution]

Portfolio items carry status across cycles: proposed → approved → in-progress → launched → sunset

Integration Notes

With discovery-analyst: PORT-XXXX (status=approved) → product intent for discovery phase. Discovery-analyst cites PORT-XXXX as input source. With rd-innovator: VIS-XXXX + PORT-XXXX define R&D direction. TECH-XXXX (adopted) feeds back into portfolio feasibility. With gtm-executor: BUSINESS_MODEL.md + PORTFOLIO.md inform GTM strategy. GROW-XXXX results feed portfolio pivots. With business-operations: Strategic OKRs cascade into OKR.md. FIN-XXXX constraints inform portfolio prioritization. With observability-planner: Production metrics (MET-XXXX) validate product-market fit assumptions. With release-manager: Release cadence informs portfolio timeline commitments.

Halt Conditions

  • Portfolio item with no strategic rationale (VIS-XXXX or stakeholder directive)
  • Business model revenue assumption unvalidated with no validation plan
  • Competitive positioning claim with no evidence
  • Fundraising metric not traceable to source artifact
  • Strategic goal with no measurable success criteria

Output Summary

Produce:

  1. VISION.md -- VIS-XXXX strategic goals with evidence + assumptions
  2. BUSINESS_MODEL.md -- BM-XXXX Business Model Canvas components
  3. PORTFOLIO.md -- PORT-XXXX prioritized portfolio with strategic rationale
  4. INVESTOR_LOG.md -- INV-XXXX fundraising tracking (if applicable)
  5. Strategy Summary -- For Business Gate 0 approval
  6. BUSINESS_DECISION_LOG.md -- Append-only strategic decision log

Stored in .agile-v/business/. All downstream skills reference these artifacts by file path.

Frequently asked questions

What does the Venture Strategist AI skill do?

Converts vision and market opportunity into traceable business models, product portfolios, and strategic plans. Use when defining business strategy, product direction, competitive positioning, or fundraising materials.

Why use Venture Strategist on TypingMind?

Because you install it once and use it with any model. Venture Strategist is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Venture Strategist in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Agile-V/agile_v_skills/tree/main/venture-strategist. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Venture Strategist?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Venture Strategist?

As many as you like. As long as a model supports skills, you can use Venture Strategist with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Venture Strategist AI skill free?

Yes. It is published on GitHub by Agile-V under the CC-BY-SA-4.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇