skills.rest
CornFedKratos
CornFedKratosCOMMUNITY
Explore all skills by this author →
GitHub

aidlc-cto

Codify CTO governance for traceable architectural decisions in AI-DLC projects.

Updated Apr 11, 2026
Search Tags:#architecture#cto#kb#annotation#collision-detection#execution-agents
One-click install
npx skills add https://github.com/CornFedKratos/s3-aidlc --skill aidlc-cto
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aidlc-cto
Source: https://github.com/CornFedKratos/s3-aidlc/tree/main/plugins/s3-aidlc/skills/aidlc-cto
Command: npx skills add https://github.com/CornFedKratos/s3-aidlc --skill aidlc-cto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Codifies CTO governance to ensure traceable, defensible architectural decisions in AI-DLC projects.

Core Features & Use Cases

  • Provides a comprehensive framework for CTO identity, authority, and hard rules that govern how decisions are made and documented.
  • Enforces the separation of responsibilities between CTO and other executive roles (CPO, CQO, CDO) to reduce scope creep.
  • Keeps an auditable KB of decisions, annotations, collision checks, and session metadata to support reviews and learning.

Quick Start

Execute the CTO annotation workflow, then perform collision detection and obtain orchestrator approval before any code is written.

Frequently Asked Questions about aidlc-cto

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce traceable architectural decisions in AI development lifecycle projects?▼

You can enforce traceable architectural decisions by codifying CTO governance rules that require annotation-before-code, collision detection, and orchestrator approvals to maintain mainline stability and auditability across AI-DLC phases.

What is annotation-before-code in AI development governance?▼

Annotation-before-code is a strict CTO governance protocol requiring architectural annotations to be documented and approved before any code is written, ensuring defensible and traceable decisions in AI-DLC projects.

How do I prevent scope creep between CTO and other executive roles in AI projects?▼

Prevent scope creep by enforcing a strict separation of responsibilities between the CTO and other executive roles like CPO, CQO, and CDO, codifying authority boundaries and hard rules for architectural governance.

How do I maintain an auditable knowledge base for AI architectural decisions?▼

Maintain an auditable KB by keeping records of architectural decisions, annotations, collision checks, and session metadata, which supports reviews and learning while ensuring strict compliance with governance protocols.

Does CTO governance require orchestrator approval before coding in AI-DLC?▼

Yes, CTO governance requires orchestrator approval alongside collision detection checks before any code is written, ensuring all architectural decisions are defensible and mainline stability is maintained.

When do I need collision detection in AI development lifecycle architecture?▼

Collision detection is needed after executing the CTO annotation workflow and before any code is written, serving as a mandatory check to prevent architectural conflicts and ensure orchestrator approval compliance.

Related Skills

Explore More Software Engineering Skills→
hpsgdhpsgd

decompose-initiative

Decompose product initiatives into structured workstreams with ownership and sequencing.

Official
Advanced
LazyNinja435LazyNinja435
1

Huddle

Synthesize session logs and decision records for persistent architectural guidance.

Community
Intermediate
CornFedKratosCornFedKratos

aidlc-project-touchchain

Coordinate AI-DLC delivery through gate-based touchchain with multi-role transitions.

Community
Advanced
scanadyscanady

tech-arch-architecture-decision-records

Create and index Architecture Decision Records using MADR and other templates.

Community
Advanced