菜单
Use when verified work is ready to land — turns it into a clean branch, commits, and a pull request whose body is drawn from the Spine (criteria, decisions, evidence). Refuses to ship work that hasn't passed verify. Reads the Spine; writes the shipped status back to it.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use right after a VC meeting to turn raw memory into a structured debrief — a signal read (interest vs. hesitation vs. pushback), the open diligence queue with draft answers, a send-ready follow-up email, and a clear recommended next step. Run within 24 hours; the follow-up email degrades fast. Use when asked to "debrief the meeting", "how did the pitch go", "write the follow-up email", or "what do I do after the meeting with <fund>".
Use to see the whole raise at a glance and to produce an investor-ready dossier — scans the .spine/raise/ namespace, builds a pipeline status tracker (every fund's scores, stage, and next action), and assembles a consolidated dossier suitable for sharing with an investor or advisor. Use when asked to "show the pipeline", "raise status", "track the funds", "what's stale", or "generate the investor report".
Use to analyse a VC term sheet — benchmarks every clause against current market norms, flags founder-unfriendly terms, scores founder-friendliness out of 100, and produces a ranked negotiation priority list with suggested pushback language. Informational only, not legal advice. Use when asked to "analyse this term sheet", "review the term sheet", "is this term sheet fair", or "what should I negotiate".
Use to turn a fund dossier into ready-to-send outreach — a cold email, a warm-intro request your contact can forward, and a LinkedIn DM, each built on the fund's own thesis language, plus a fund-specific one-pager. Refuses to draft for a no-go fund. Drafts only — it never sends. Use when asked to "draft outreach for <fund>", "write the intro email", "cold email this VC", or "make a one-pager for <fund>".
Use to prepare for pitching — full-spectrum prep in one skill. With no fund, it runs the stress-test: ten lethal questions a hostile VC would ask (know what to defend) and ten strongest signals a champion would champion (know what to lead with). With a fund, it builds a timed meeting plan with segment scripts, preemptive answers to that fund's diligence questions, and red-flag rebuttals. Use when asked to "prep me to pitch", "stress-test my pitch", "destroy my startup", "what are my strongest signals", or "prep for the meeting with <fund>".
Use to research the VC landscape and build a ranked pipeline of funds to target — produces 15–20 funds in three tiers (pursue now, warm up first, monitor) with a fit rationale and a contact angle for each. Run before vetting and matching individual funds. Use when asked to "build a target list", "which VCs should we approach", "find funds for us", or "research the VC landscape".
| name | ship |
| description | Use when verified work is ready to land — turns it into a clean branch, commits, and a pull request whose body is drawn from the Spine (criteria, decisions, evidence). Refuses to ship work that hasn't passed verify. Reads the Spine; writes the shipped status back to it. |
Shipping is a claim to the rest of the team: this is done, here's the proof, here's why. This skill assembles that claim from the Spine instead of from memory.
journal.md (acceptance criteria + the latest
verification result), conventions.md (test/build commands and any VCS or PR
conventions), context.md (shared language), and decisions/ (ADRs to cite).journal.md. If anything is unverified or failing, stop and run verify
first — do not ship unproven work.conventions.md.skills/, or the plugin/marketplace manifests
— bump the version so existing installs actually upgrade (an unchanged
version makes /plugin upgrade a silent no-op). For this repo that means the
same new version in all three places: root package.json,
.claude-plugin/plugin.json, and the .claude-plugin/marketplace.json
plugins[] entry. Use minor for a new skill or capability, patch for a
fix to an existing skill; refresh the marketplace entry's description/keywords
if the surface changed. CI's release-check enforces this on the PR, and the
validator enforces that the three versions match — do it here so the gate is
green. (Pure tooling-only changes — scripts/, .github/, .spine/, docs —
need no bump.)conventions.md one last time if CI won't.journal.md: mark the work shipped, link the
PR, and set Next step (await review / merge). Leave the merge to the user
unless they ask you to land it.journal.md (criteria + verification result), conventions.md
(commands, VCS/PR conventions), context.md (language), decisions/ (ADRs to cite).journal.md (shipped status, PR link, next step).verify hasn't passed — the PR body's evidence comes from
a real run, not an assertion.