cs-explore

Stage 1 of the codestable feature workflow that drafts a comprehensive design document (covering architecture, interface contracts, implementation hints, and test design) plus an action checklist, which serve as the single source of truth for the subsequent implementation and acceptance stages.

A knowledge-capture skill in the codestable workflow that distills engineering lessons into searchable learning documents — pitfall track records bugs, traps, and failed attempts while knowledge track records best practices and reusable patterns, so teams avoid repeating the same mistakes.

A CodeStable skill that routes bug-fix workflows through a structured three-stage process — problem report, root cause analysis, and fix verification — ensuring every bug fix leaves behind traceable documentation.

Stage 2 of the codestable feature workflow that translates an approved design document into code by following the checklist step-by-step, enforcing three core disciplines: write the minimum necessary code, only modify intended files, and never make decisions not covered by the design document.

A CodeStable skill that routes new feature development through a four-stage workflow — brainstorm, design, implementation, and acceptance — inserting a design document between requirements and code to prevent scope drift and leave behind a traceable record.

Stage 3 of the codestable issue workflow that implements targeted bug fixes according to a confirmed root-cause analysis, validates the fix, and writes a fix-note document — enforcing strict scope discipline to prevent unrelated refactoring from contaminating the fix.

A CodeStable skill that generates reference documentation for each public-facing entry of a library (components, functions, CLI commands, etc.) by reading directly from source code, with a manifest-tracked batch or single-entry workflow.

A CodeStable skill that serves as the entry point for exploratory discussions — it diagnoses vague ideas through one or two rounds of dialogue and routes them to the right downstream: directly to feature design, into a feature brainstorm note, or to roadmap decomposition for large requirements.

The final acceptance stage of the CodeStable feature workflow that verifies implementation against the design document, updates architecture and requirement docs, closes roadmap items, and produces an acceptance report as the closure record.

The root cause analysis stage of the CodeStable issue workflow — it reads the problem report and actual source code to identify the true root cause, assesses impact, and presents 2-3 fix options for the user to choose before any code is changed.