--- name: investor-ready description: "Prepare for fundraising due diligence — runs CTO, CFO, CPO, sales, and codebase health reviews to produce a consolidated investor brief with scorecard, red flags, and strengths. Use before Series A, seed round, acqui-hire evaluation, or board presentation." version: "2.0.0" category: combo platforms: - CLAUDE_CODE --- You are an autonomous investor readiness agent. Do NOT ask the user questions. Run the full executive review pipeline below and produce a consolidated investor brief suitable for due diligence. Unlike `/launch-readiness`, this pipeline does NOT stop on critical findings. Investors need the full picture — warts and all. Every phase runs to completion, and the final output presents an honest assessment. TARGET: $ARGUMENTS If arguments are provided, use them as context (e.g., "Series A prep", "acqui-hire evaluation", specific focus areas). If no arguments, run the full investor readiness assessment. ============================================================ PHASE 1: TECHNICAL DUE DILIGENCE (/cto-review) ============================================================ Follow the instructions defined in the `/cto-review` skill exactly. Evaluate from a Chief Technology Officer perspective: - Architecture quality and scalability headroom - Tech debt burden and maintenance trajectory - Code quality, test coverage, and engineering practices - Infrastructure maturity and operational readiness - Security posture and compliance foundations - Team velocity signals (git history, commit patterns, deploy frequency) Record the CTO verdict, risk assessment, and all findings. ============================================================ PHASE 2: FINANCIAL REVIEW (/cfo-review) ============================================================ Follow the instructions defined in the `/cfo-review` skill exactly. Evaluate from a Chief Financial Officer perspective: - Infrastructure cost structure and unit economics indicators - Revenue model implementation (pricing, billing, subscription logic) - Cost scaling trajectory (how costs grow with users) - Financial controls (usage limits, spending caps, rate limiting) - Margin indicators (compute cost per user, third-party fees) - Cash efficiency signals (build vs buy decisions, dependency costs) Record the CFO verdict, financial risk assessment, and all findings. ============================================================ PHASE 3: PRODUCT ASSESSMENT (/cpo-review) ============================================================ Follow the instructions defined in the `/cpo-review` skill exactly. Evaluate from a Chief Product Officer perspective: - Product vision clarity and market positioning - Feature completeness and roadmap maturity - User experience quality and design coherence - Product-market fit signals in the codebase - Competitive differentiation (what's unique, what's commodity) - Growth mechanics and network effects potential Record the CPO verdict, product risk assessment, and all findings. ============================================================ PHASE 4: GO-TO-MARKET READINESS (/sales-readiness) ============================================================ Follow the instructions defined in the `/sales-readiness` skill exactly. Evaluate sales and go-to-market readiness: - Pricing page and plan architecture - Self-serve vs sales-assisted flow - Trial and conversion infrastructure - Documentation and collateral completeness - Integration ecosystem and API maturity - Enterprise readiness (SSO, RBAC, compliance badges) Record the sales readiness score and all findings. ============================================================ PHASE 5: ENGINEERING QUALITY (/codebase-health) ============================================================ Follow the instructions defined in the `/codebase-health` skill exactly. Produce a quantitative codebase health assessment: - Lines of code, file count, language distribution - Test coverage and test quality - Dependency count and freshness - Code complexity metrics - Documentation coverage - TODO/FIXME/HACK density - Commit history health (frequency, message quality, contributor distribution) Record the codebase health score and all metrics. ============================================================ PHASE 6: INVESTOR BRIEF SYNTHESIS ============================================================ Synthesize all 5 phases into a single investor-ready document. Step 6.1 -- Executive Summary Write a 3-paragraph executive summary that an investor can read in 60 seconds: - Paragraph 1: What the product does and its current state - Paragraph 2: Key strengths (what's working well, defensible advantages) - Paragraph 3: Key risks (honest assessment of weaknesses and unknowns) Step 6.2 -- Scorecard Produce a consolidated scorecard across all dimensions: | Dimension | Score | Risk Level | Key Finding | |-----------|-------|------------|-------------| | Technical Architecture | {1-10} | {Low/Med/High} | {one-line} | | Code Quality | {1-10} | {Low/Med/High} | {one-line} | | Financial Efficiency | {1-10} | {Low/Med/High} | {one-line} | | Product Maturity | {1-10} | {Low/Med/High} | {one-line} | | Market Readiness | {1-10} | {Low/Med/High} | {one-line} | | Engineering Velocity | {1-10} | {Low/Med/High} | {one-line} | | Security & Compliance | {1-10} | {Low/Med/High} | {one-line} | | Scalability | {1-10} | {Low/Med/High} | {one-line} | | **Overall** | **{avg}** | **{level}** | **{verdict}** | Step 6.3 -- Red Flags List every finding that an investor would consider a red flag: - Technical: single points of failure, no tests, security gaps - Financial: unbounded costs, no revenue model, expensive dependencies - Product: unclear value prop, missing core features, poor UX - Market: no distribution strategy, missing enterprise features - Team: bus factor concerns (single contributor patterns) Step 6.4 -- Strengths List every finding that an investor would consider a positive signal: - Clean architecture, strong test coverage, modern stack - Clear revenue model, healthy unit economics - Strong product vision, good UX, clear differentiation - Growth mechanics, viral loops, network effects - Active development, fast iteration, good engineering practices Step 6.5 -- Write Report Write the complete investor brief to `docs/investor-brief.md` in the project (create the `docs/` directory if it doesn't exist). ============================================================ SELF-HEALING VALIDATION (max 3 iterations) ============================================================ After completing all phases, validate the combined output: 1. Re-run the specific checks that originally found issues to confirm fixes. 2. Run the project's test suite to verify fixes didn't introduce regressions. 3. Run build/compile to confirm no breakage. 4. If new issues surfaced from fixes, add them to the fix queue. 5. Repeat the fix-validate cycle up to 3 iterations total. STOP when: - Zero Critical/High issues remain - Build and tests pass - No new issues introduced by fixes IF STILL FAILING after 3 iterations: - Document remaining issues with full context - Classify as requiring manual intervention or architectural changes ============================================================ OUTPUT ============================================================ ## Investor Readiness Assessment Complete ### One-Page Investor Brief **Product:** {product name} **Stage:** {prototype/MVP/growth/mature} **Stack:** {tech stack summary} **Executive Summary:** {3-paragraph summary from Step 6.1} ### Scorecard {Table from Step 6.2} **Overall Investor Readiness: {NOT READY / EARLY STAGE / FUNDABLE / STRONG}** - NOT READY: Score < 4 or 3+ red flags with no mitigations - EARLY STAGE: Score 4-5, addressable gaps, needs runway to mature - FUNDABLE: Score 6-7, solid foundation, clear path to scale - STRONG: Score 8+, exceptional engineering and product quality ### Red Flags ({N}) {List from Step 6.3} ### Strengths ({N}) {List from Step 6.4} ### Phase Details | Phase | Skill | Verdict | Findings | |-------|-------|---------|----------| | 1 | /cto-review | {verdict} | {N critical, N high, N medium} | | 2 | /cfo-review | {verdict} | {N critical, N high, N medium} | | 3 | /cpo-review | {verdict} | {N critical, N high, N medium} | | 4 | /sales-readiness | {verdict} | {N critical, N high, N medium} | | 5 | /codebase-health | {score}/10 | {key metrics} | ### Report saved to: `docs/investor-brief.md` ============================================================ ============================================================ SELF-EVOLUTION TELEMETRY ============================================================ After producing output, record execution metadata for the /evolve pipeline. Check if a project memory directory exists: - Look for the project path in `~/.claude/projects/` - If found, append to `skill-telemetry.md` in that memory directory Entry format: ``` ### /investor-ready — {{YYYY-MM-DD}} - Outcome: {{SUCCESS | PARTIAL | FAILED}} - Self-healed: {{yes — what was healed | no}} - Iterations used: {{N}} / {{N max}} - Bottleneck: {{phase that struggled or "none"}} - Suggestion: {{one-line improvement idea for /evolve, or "none"}} ``` Only log if the memory directory exists. Skip silently if not found. Keep entries concise — /evolve will parse these for skill improvement signals. STRICT RULES ============================================================ - ALL 5 phases must run to completion. Do NOT stop on critical findings. - Each phase MUST run the referenced skill's full instructions. - Be brutally honest. Investors lose money on sugar-coated assessments. - Every red flag must reference specific files or code patterns. - The executive summary must be readable by a non-technical investor. - The scorecard must be defensible -- explain any score above 7 or below 4. - If a referenced skill does not exist yet, skip that phase with a "SKIPPED -- skill not available" status and note it as a gap. - Do NOT propose code changes. This is an analysis pipeline, not a fix pipeline. - Credit genuine strengths equally with flagging weaknesses. NEXT STEPS: - "Address red flags with `/iterate` before the investor meeting." - "Run `/launch-readiness` to verify the product is shippable." - "Run `/compete` to strengthen the competitive positioning section." - "Run `/cost-analysis` to add detailed unit economics to the financial section." - "Run `/stress-test-personas` to pressure-test the product from 6 additional angles."