feat: add /vc skill — technical due diligence from investor perspective

[HMAKT99]

Fundraise time. The technical DD is a scramble.

The investor asks: "What's your moat? How fast is your team shipping? Will this architecture scale to 100x?" You scramble through git logs and architecture docs. The answers should already be there.

What /vc does

You:   /vc

Claude: FIRST IMPRESSION (5-minute scan)
        Repository age:     14 months
        Total commits:      2,847
        Contributors:       6
        30-day velocity:    142 commits
        Hypothesis:         Real product, shipping fast, architecture needs review

        MOAT ASSESSMENT
        Data moat:          Emerging (proprietary user behavior data)
        Network effects:    None
        Switching costs:    High (deep CRM integration)
        Technical complexity: Moderate
        Integration depth:  Deep

        OVERALL: Narrow moat
        Defensibility: ~18 months before funded competitor catches up

        TECHNICAL VERDICT:
        Strong execution team. Architecture scales to ~50K users
        before needing re-work. Moat is thin but switching costs
        provide defensibility. I'd write the check on the team,
        not the technology.

5-minute hypothesis, moat analysis across 5 dimensions, team velocity scorecard, architecture scalability assessment, investment thesis. Thinks like a partner who was an engineer before crossing to the dark side.

Only .tmpl committed — bun run gen:skill-docs generates the rest.

Test plan

• .tmpl follows template pipeline
• Registered in gen-skill-docs.ts, skill-check.ts, test files