Accidental Cio
Apply Scott Millett's "The Accidental CIO — A Lean and Agile Playbook for IT Leaders" (Wiley, 2024) when designing or reviewing how a technology organisation decides, funds, governs and delivers work. Covers the five components of an adaptive IT operating model (organised, work, govern, talent, lead) and its four themes (outcomes over output, intrinsic motivation, being not doing agile, manage flow not people); matching method and governance to context via Cynefin and Wardley evolution; governance as demand management + funding + measurement + decision rights, shifting from project funding to
Install
/plugin marketplace add vnovakovits/claude-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add vnovakovits/claude-skills --skill accidental-ciogit clone --depth 1 https://github.com/vnovakovits/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/plugins/engineering-practices/skills/accidental-cio ~/.claude/skills/accidental-cioPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# The Accidental CIO (Scott Millett) Apply this skill when someone is designing or reviewing *how a technology organisation works* — its intake and prioritisation process, funding model, governance, team structure, decision rights, strategy or roadmap — rather than the code itself. It is the operating-model lens: the layer above `kanban`, `flow-efficiency` and `continuous-delivery`, and the layer below business strategy. ## Core Philosophy **The problem is the system, not the people.** Most IT dysfunction — order-taking, missed dates, "the business vs IT", busy teams that deliver little — is produced by the operating model: how work is requested, funded, governed, staffed and led. Changing practices (standups, boards, sprints) without changing the system changes nothing. Millett leans on Deming, Ackoff and systems thinking: *a system is the product of the interactions of its parts, not the sum of them.* **Service provider vs disruptor is a false choice.** The old mental model lets a CIO be either the efficient utility (keep the lights on, cut cost) or the innovator. Millett's position: IT must do both, and the operating model must be *ambidextrous* — different sub-models for different kinds of problem, held together by shared strategic intent.
Details
- Skill name
accidental-cio- Repository
- vnovakovits/claude-skills
- Path
plugins/engineering-practices/skills/accidental-cio/SKILL.md- License
- MIT
- Repo updated
- 16 November 2026
FAQ
What does the Accidental Cio skill do?
Apply Scott Millett's "The Accidental CIO — A Lean and Agile Playbook for IT Leaders" (Wiley, 2024) when designing or reviewing how a technology organisation decides, funds, governs and delivers work. Covers the five components of an adaptive IT operating model (organised, work, govern, talent, lead) and its four themes (outcomes over output, intrinsic motivation, being not doing agile, manage flow not people); matching method and governance to context via Cynefin and Wardley evolution; governance as demand management + funding + measurement + decision rights, shifting from project funding to
How do I install the Accidental Cio skill?
Claude Code plugin: /plugin marketplace add vnovakovits/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Accidental Cio popular?
It lives in vnovakovits/claude-skills, which has 5 GitHub stars and 2 forks.
Related skills
Agent Retro
5vnovakovits/claude-skills
Run a retrospective on a coding-agent session and improve the agent's environment, not the code. Combines Derby & Larsen's five-stage retrospective, Shigeo Shingo's poka-yoke (turn a mechanical mistake into a check that makes it impossible), and Matt Pocock's retro categories — navigation, automated checks, coding standards, steering files, tool economy, information access. Covers mining the session transcript for corrections, wrong turns and slow searches; deciding where each fix belongs (analyzer, hook, CI, reviewer standards, CLAUDE.md pointer, skill, doc or memory); the no-op test for stee
API Design
5vnovakovits/claude-skills
Design APIs that are clear, evolvable, and idiomatic to their protocol — covering REST (Fielding, Richardson Maturity Model, Massé), GraphQL, gRPC/protobuf, versioning strategies, pagination, error responses (RFC 7807 Problem Details), idempotency, authentication, documentation (OpenAPI), and the pragmatic trade-offs between RESTful purity and developer ergonomics. Use when designing a new endpoint, choosing between REST/GraphQL/gRPC, defining versioning, structuring error responses, deciding pagination strategy, or evaluating an existing API's evolvability.
Architecture Decision Records
5vnovakovits/claude-skills
Apply Michael Nygard's Architecture Decision Records (ADRs) — lightweight, immutable Markdown documents that capture significant architectural decisions, their context, and their consequences. Covers Nygard's classic format, MADR, when a decision is "architecturally significant", supersession workflow, where to store ADRs, and how to use them as living institutional memory. Use when making a significant technical decision, when joining a project and wondering "why was it built this way", when a past decision starts to bite, or when a team's tribal knowledge is bleeding away through personnel t
Brand Guidelines
8Freddy-CHEN-ux/00_claude_skills
Establish or analyze brand identity guidelines. Creates comprehensive brand documentation that frontend-design, testing, and other skills automatically reference for consistent execution.
Search Repair Guides
9Lord1Egypt/RA-Skills
Search iFixit for repair guides by device model, brand, or category and return structured results — title, difficulty, time, step count, tools, parts, and direct guide URL — plus optional full step-by-step instructions with image URLs. Read-only.
Design Md
5bolasblack/claude-skills
Create, update, validate, diff, or export DESIGN.md files following the Google Stitch DESIGN.md spec and @google/design.md tooling. Use when the user asks to write/update DESIGN.md, create a design system document, generate design tokens, encode brand/UI guidelines, export a design system, or document UI consistency rules for AI agents. Do NOT use for ordinary UI implementation unless the user asks for DESIGN.md or design-system documentation.
Browse the most popular Claude skills, all frontend & design skills, or write your own with the skills generator.