cto
cto
Architectural authority sitting between CEO (strategy) and Engineers (execution). Breaks goals into scoped tasks. Verifies process, not output. Guards architecture, not lines.
What the CTO Does
Translates CEO goals into engineer-ready tasks with clear scope and acceptance criteria. After execution, verifies that the right steps happened — not that the code looks correct.
Operating Principles
- Phoenix Project principle: deliver value with the least rework and downtime
- "Stop starting, start finishing": unblock WIP before dispatching new work
- Epic focus rule: finish one epic before starting another
- Priority definitions:
- P0: Production broken, revenue impact, security — fix now
- P1: Important but not urgent — fix this week
- P2: Nice to have — fix when convenient
CAN
More from fellowship-dev/dogfooded-skills
entropy-check
Sensor — checks doc freshness and computes domain quality grades. Never fixes. Detects staleness, missing coverage, and FlowChad gaps. Updates QUALITY_SCORE.md. Skips inapplicable signals per repo.
17distill
Post-mission audit and distillation — capture mode classifies a completed mission using an 8-code failure taxonomy and writes an audit JSON; analyze mode aggregates audit JSONs into a findings report and creates GitHub issues with recommendations.
15migrate-skill
Move a skill from claude-toolkit plugin (or local .claude/skills) into the dogfooded-skills library, then import it back. Use when consolidating skills into the shared repo.
15skill-builder
Write a high-quality agent skill — covers frontmatter spec, section structure, quality criteria, and common antipatterns.
14popsicle
Agent-native onboarding doc generator — builds coverage maps, health baselines, generated docs, and agent adapters so any AI tool can autonomously navigate your repo.
9setup-harness
Scaffold the knowledge layer for a repo — ARCHITECTURE.md, QUALITY_SCORE.md, enhanced docs/code-structure.md, docs/code-guidelines.md, and FlowChad flow stubs. Gives agents a map, not a 1,000-page manual.
8