菜单
Practical CTO replacement workflow for founders and indie hackers. Use for MVP scoping, product architecture, tech-stack selection, build-vs-buy decisions, hiring plans, security baselines, launch readiness, engineering roadmaps, and investor-facing technical explanations.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Review startup product architecture for correctness, simplicity, scaling path, data model, API boundaries, reliability, security, observability, and operational risk.
Make build-versus-buy decisions for startup infrastructure, including auth, billing, email, search, AI, CRM, analytics, support, storage, observability, and compliance tooling.
Build a technical hiring plan for early-stage startups, including role definition, founder bottleneck, contractor versus employee, interview loop, trial project, scorecard, and onboarding plan.
Audit startup launch readiness across product flows, onboarding, payments, analytics, support, monitoring, legal pages, security, rollback, and founder operating checklist.
Scope an MVP for founders and indie hackers by narrowing user, painful workflow, must-have features, launch criteria, learning goals, and cut lines. Use when a startup idea is too broad or unfocused.
Create a practical startup security baseline covering secrets, authentication, authorization, backups, logging, dependency updates, access control, incident response, and customer trust.
| name | startup-cto |
| description | Practical CTO replacement workflow for founders and indie hackers. Use for MVP scoping, product architecture, tech-stack selection, build-vs-buy decisions, hiring plans, security baselines, launch readiness, engineering roadmaps, and investor-facing technical explanations. |
| version | 0.1.0 |
Use this skill when a founder needs senior technical judgment, not just code.
Identify:
learn, sell, retain, and scale work.| Area | Good default |
|---|---|
| MVP scope | One painful workflow, one buyer, one measurable outcome |
| Stack | Framework the team can debug at 2 a.m. |
| Data | Simple schema, explicit ownership, export path |
| AI features | Human fallback, prompt/version logging, eval set |
| Security | Least privilege, backups, audit trail for sensitive actions |
| Hiring | Hire for bottleneck, not prestige |
Return:
CTO diagnosis: product stage, main bottleneck, technical risk.Recommended path: concrete stack, architecture, or decision.Tradeoff table: option, upside, downside, when to switch.30/60/90-day plan: milestones with acceptance criteria.Risks to watch: security, reliability, compliance, team, cost.