wang-cankun/ckstack

Explain how code, a system, or an analysis workflow operates by tracing its implementation. Use for runtime or data flow walkthroughs, subsystem onboarding, and placement or ownership questions. Use ck-why for historical rationale.

Trace what a proposed or implemented change could break beyond its immediate callers, and test the assumptions its safety depends on. Use for impact analysis, compatibility questions, or a small-looking change with uncertain downstream effects.

Build disposable prototypes or small experiments to settle a design or behavioral question through observation. Use when the user asks to prototype, mock up, try competing approaches, or compare layouts, interactions, methods, or workflow behavior before implementation.

Reflect on completed work or recurring friction to identify evidence-backed lessons and their smallest useful repair. Use for session retrospectives, learning from user corrections, or improving a workflow from observed failures and successes.

Create, revise, and evaluate reusable agent skills. Use for skill authoring, unreliable skill behavior, version comparisons, or trigger tuning; use a skill manager for installation and retirement.

Establish a repeatable project verification method from real user paths, reusing existing checks and creating a skill only for a useful gap. Use when verification knowledge is missing or hard to reuse for an app, CLI, library, service, or analysis workflow.

Maintain a project's verification skill, harness, and feature map after a concrete change, or audit the full map against source and live behavior. Use when verification recipes drift or need a coverage audit.

Investigate the historical rationale behind code, a design, or an analysis choice using source history and relevant records. Use for why a choice was made, rejected alternatives, defensive code, and the origin of thresholds or methods. Use ck-how for mechanics.