ck-methodology

Prevent architectural drift in multi-session software engineering by enforcing a document-driven collaboration protocol. This approach standardizes workflows using a structured phase-gate system to ensure deterministic progress and verifiable observation-based testing.

Manage stale documentation in complex software campaigns by enforcing a strict lifecycle for campaign artifacts like PROMPT.md, PLAN.md, and PROGRESS.md. This staleness management protocol prevents outdated information from misleading future development sessions.

Structure engineering workflows for architectural changes by organizing work into verifiable phase-gates. This ensures each step is documented, tested, and reviewed before proceeding, satisfying requirements for CTO-level oversight and rigorous state tracking.

You need a phase-gate system when handling complex, long-running software development campaigns requiring deterministic progress. It is essential for multi-session tasks involving architectural changes or new module creation that demand CTO-level oversight and strict state tracking.

Resolve technical blockers in multi-session engineering workflows by using a dedicated stuck protocol. This provides a non-silent path for resolving issues through research, pivot documentation, and CTO-level review to maintain project context.

This engineering methodology is designed for complex, multi-session software development campaigns requiring rigorous state tracking. It is not suited for short-running tasks, as the document-driven protocol and phase-gate system enforce CTO-level oversight overhead.