great_cto
FeaturedUse when the CTO describes a feature, task, or project goal. Orchestrates the full SDLC pipeline automatically based on project type.
Install
Quality Score: 88/100
Skill Content
Details
- Author
- avelikiy
- Repository
- avelikiy/great_cto
- Created
- 5 months ago
- Last Updated
- today
- Language
- JavaScript
- License
- MIT
Integrates with
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
cto-cycle
Use when building any new feature, change, or fix in ANY project that you want done properly — invoked by saying "use the cto-cycle", "run the CTO cycle", "build X with the CTO", or "/cto-cycle". Project-agnostic: it first orients on the current repo (CLAUDE.md, rules, plan docs, stack) and then runs a disciplined loop — investigate the scope, interview the user to kill assumptions, write an implementation plan, have the CTO sub-agent review and score it (0–100), debate to consensus, then implement phase-by-phase with a CTO review after each phase — advancing autonomously without waiting between phases. Supports an optional external deep-audit reviewer and optional email summaries.
cto
Startup / AI-startup CTO who is also a top-tier individual contributor. Two modes: (1) greenfield — turn fuzzy business intent into a buildable design (brief.md, arch.md, specs/) through conversation; (2) brownfield — work hands-on inside an existing codebase: investigate, recommend, refactor, write features, debug, ship PRs, update ADRs and plan docs. Trigger when the user wants to build something new ('I want to build', 'help me design', '我想做', '帮我想想这个怎么做'), AND trigger when the user invokes /cto on an existing codebase for architecture work, migrations, refactors, debugging, or any senior-IC task they want CTO-level judgment and execution on. Do NOT trigger for trivial one-off coding questions where no architectural judgment is needed.
cto
DEFAULT ENTRY POINT for engineering work — building a feature, starting a new app or product, or fixing a bug end-to-end. Runs a gated idea→spec→build→review→QA→ship pipeline. Use for requests like "build X", "add feature Y", "new app for Z", or when work should end deployed and verified. For pure visual/design work use a design skill; for a one-off diff review use eng-review directly.