v1.1.0

[zszendro]

A content release that turned into a correctness one. If you installed via git clone into your skills directory, it never worked — see Fixed below.

Added

Four new challenge surfaces, taking the library from 16 to 20:

• Timing — the "why now?" question, and the prior-attempts graveyard most founders can't name
• Platform dependency — separating price risk (survivable, modellable) from existence risk (not)
• AI-native risk — whether a product rides model improvement or gets absorbed by it, plus model commoditisation and accuracy economics
• Atoms and capital intensity — hardware, inventory and long-R&D arithmetic, closing a gap the contributing notes had admitted to

Three new moat patterns, taking the set from 9 to 12: embedded distribution, proprietary model or eval set (the AI-era counterpart to "generate the data"), and regulatory or license position. "Sequence the moat" renumbers to 12 to stay last as the capstone.

A worked example — references/example-teardown.md. One idea run end to end, with 14 footnoted sources rather than illustrative figures. The research inverted the verdict: the idea as briefed turned out to be a competitor's core product funded at ~$85M, the "nobody has this data" moat was false, and the city that motivated it had already cut review times from 15 weeks to 3. Which is the point — that's what a real teardown does.

A conversational close. Delivery now names the one or two things the analysis is least sure about, then offers three or four specific next steps: expand a named challenge, a PDF, a one-page executive summary, a deck outline, re-run the economics on your numbers, or a teardown of the reframe itself.

Fixed

The Claude Code install instruction never worked. Personal skills resolve at ~/.claude/skills/<name>/SKILL.md and discovery does not recurse, so cloning this repo's root put SKILL.md one directory too deep. There was no error — the skill simply never appeared. Use the symlink route in the README instead, which also makes git pull the update path.

The Claude apps instruction described a flow that doesn't exist. The real path is Customize → Skills → Add → Upload a skill. The README now also explains that this is a cloud upload stored against your account — which is why no local folder appears after installing that way — along with the plan requirements and the fact that the two install routes don't sync.

Changed

• Version metadata now ships in SKILL.md under metadata, deliberately not as a top-level version: key — that would break .skill packaging and claude.ai upload, which validate against the six-field Agent Skills spec.
• scripts/validate.py and scripts/package.sh make the bundle reproducible, with validation that fails the build rather than the upload.
• Guards so the worked example can't shorten output: one section at full depth as a density reference, explicit length markers on the rest, and the word target restated in SKILL.md. Verified end to end — 5,933 words with every section intact, from a run given no hint that length was being measured.
• The word range is explicitly not a target to iterate against. Testing found the model spending ten minutes in compression passes without converging; a stall is worse than a plan that runs long.

Install

Download vc-teardown.skill below, then Customize → Skills → Add → Upload a skill. Requires a Pro, Max, Team or Enterprise plan with code execution enabled.

For Claude Code, use the symlink route in the README.

---

v1.0.1 remains published and downloadable here.

---

This discussion was created from the release v1.1.0.