CTO Kit

#Playbook

Click a step to see exactly what to run and what you get back. Do them in order on your first week; re-run them as the cadence suggests after that.

1. 01
   Scope the next 2-week build· 20 min · per feature

   Runmvp-scopeSkill
   When

   Start of any new feature bigger than a hotfix.

   You type

   "scope the referral MVP — target ship by Friday week 2"

   You get

   A spec with one user story, the smallest shippable surface, a NOT-in-MVP list, and a kill criterion if scope creeps >20%.

   Next step
2. 02
   Decide before you code· 10 min · ad-hoc

   RunadrSkill
3. 03
   Review a diff before merge· 5 min · per PR

   Runcode-reviewSubagent
4. 04
   Pick a stack or a library· 15 min · ad-hoc

   Runstack-advisorSkill
5. 05
   Build it or buy it· 10 min · ad-hoc

   Runbuild-vs-buySkill
6. 06
   Stop tech debt from eating the roadmap· 20 min · weekly

   Runtech-debt-triageSkill

#MCPs to connect

Optional. Pick one or two to start — the kit works without them, it just gets sharper with your real data.

• GitHubcode-review subagent reads the diff directly. adr skill writes to docs/adr/ in your repo.Docs
• Linearmvp-scope pulls your feature list and writes back the cut version tagged 'not in MVP'.Docs
• Sentrytech-debt-triage pulls top error frequencies + user counts to score what actually hurts.Docs
• VercelDeploy + rollback context for incident post-mortems. Links errors to specific deployments.Docs
• PostgreSQL (your DB)build-vs-buy asks it whether you can answer your question with existing tables before building a new feature.Docs

#All assets reference

Every skill, subagent, and command in this kit — click one for full detail, examples, and pitfalls.