skills/mine/vc-strategy/SKILL.md
Assess fundability, positioning, fundraising narrative, timing, round size, instruments, valuation, dilution, milestones, and term negotiation, including devtools/AI infrastructure. Excludes deck authoring and outreach execution.
npx skillsauth add pedronauck/skills vc-strategyInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Answer the founder's actual financing or positioning question with evidence and explicit assumptions. Use only the relevant branch; a one-liner, valuation question, or term-sheet clause does not require an entire fundraising memo.
| Question | Reference |
| --- | --- |
| Whether/when VC fits | references/what-vcs-evaluate.md |
| Narrative or value proposition | references/narrative-playbook.md |
| Amount, runway, milestones, dilution | references/round-design.md |
| Instrument or term sheet | references/deal-terms.md |
| Current market comparison | references/stage-benchmarks.md |
| Devtools/AI-infra positioning | references/devtools-positioning.md |
Read matching sections and reuse known company facts. Current financial/legal guidance and market claims require authoritative, current sources; bundled numbers retain their dates and limitations. Fund-return, ownership, readiness, and sizing rubrics are diagnostic tools, not fixed approval thresholds.
For a full round design, connect cash/burn, credible milestones, timing, alternatives, and dilution. Model every existing SAFE when conversion or cap-table outcomes are in scope. Cross-check estimates where assumptions differ; do not force three methods to converge within an arbitrary percentage. Compare scenarios when they illuminate a real tradeoff.
Keep economics separate from control rights, state risks and uncertainty, and use qualified legal review for binding instrument/term decisions. Do not fabricate traction, accepted valuation, investor appetite, or expected returns. Recommend non-VC alternatives when the company's needs fit them better.
Deliver the requested answer or strategy artifact with the reasoning and material gaps. Deck creation and outreach remain separate tasks unless included in the user's request.
testing
Assess DDD fit; discover domains with EventStorming, define language and bounded contexts, and design aggregates, value objects, events, and repositories. Excludes architecture-only audits, product specs, and CQRS/Event Sourcing catalogs.
development
Build terminal UIs with ratatui following 2026 Rust best practices. Use when: (1) Creating new TUI apps, (2) Adding widgets/layouts, (3) Keyboard navigation/state management, (4) Image integration via ratatui-image, (5) Async event handling, (6) Release optimization. Covers v0.30.0+ API, Elm Architecture, StatefulWidget, color-eyre.
development
Find 10x product opportunities and high-leverage improvements. Use when user wants strategic product thinking, mentions '10x', wants to find high-impact features, or says 'what would make this 10x better', 'product strategy', or 'what should we build next'.
development
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.