cs

cs-xxx

cs

1. When users come with specific requests → match the scenario routing table, tell users which

   cs-*

   to trigger, and briefly explain why
2. When users just want to learn about the system / can't clearly state what they want to do → provide a concise system overview + let users choose or describe more specific requests

codestable/

1. Check if the repository has integrated CodeStable — use

   Glob codestable/

   to see if the top-level directory exists
2. If it exists — read

   codestable/reference/system-overview.md

   (if available) as a more comprehensive system reference; use

   Glob

   on

   codestable/features/

   codestable/issues/

   codestable/roadmap/

   to see ongoing work (just get the directory names, no need to read each file)
3. If it does not exist — note this, and later prompt users to run

   cs-onboard

   first
4. Check the user's original input — is it an open-ended question or a specific request? If it's a request, match the routing table; if not, provide the system overview

codestable/

codestable/
├── requirements/    Requirement entity ("why this capability is needed", only records current status)
├── architecture/    Architecture entity ("what the system looks like now", only records current status)
├── roadmap/         Planning layer ("how to implement this large requirement next + module splitting + interface definition")
├── features/        Aggregation root for specs of new capabilities (design / impl / accept)
├── issues/          Aggregation root for specs of bug fixes (report / analyze / fix)
├── refactors/       Aggregation root for refactoring specs (beta)
└── compound/        Knowledge accumulation (learning / trick / decision / explore)

• New capability development:

  cs-feat-design

  →

  cs-feat-impl

  →

  cs-feat-accept

  (start with

  cs-brainstorm

  triage if ideas are vague)
• Bug fixing:

  cs-issue-report

  →

  cs-issue-analyze

  →

  cs-issue-fix

• Refactoring (beta):

  cs-refactor

  /

  cs-refactor-ff

cs-learn

cs-trick

cs-decide

cs-explore

compound/

If the project has been onboarded, see

codestable/reference/system-overview.md

for a more detailed overview.

• Bug →

  cs-issue

• Requirement change →

  cs-req

  (update requirement documentation) + then run

  cs-feat

  for implementation

• Review "Encountered Y when doing X" →

  cs-learn

• Prescription "Do X like this in the future" →

  cs-trick

• Rule "All projects follow X from now on" →

  cs-decide

• Investigation "What is X like now" →

  cs-explore

1. One sentence: CodeStable is an AI coding workflow for serious engineering, orchestrating the software lifecycle instead of Agents
2. Quick overview of 6 entities + 3 processes (see "Quick system overview" above)
3. Ask the user: "Where do you want to start most?" Provide three specific prompts:
   • "I have a new feature to develop" → cs-feat
   • "There's a bug in the code" → cs-issue
   • "The project hasn't integrated CodeStable yet" → cs-onboard

• Have told the user which specific

  cs-*

  sub-skill to trigger next (or confirmed that the user only came to learn about the system and doesn't want to perform tasks)

For this request, it is recommended to use

cs-xxx

— {one-sentence reason: because it specializes in handling X-type scenarios}. After triggering, it will {briefly describe what will happen: first scan existing specs / ask you to describe first / enter triage / ...}. Switch to

cs-xxx

now?

• Do not read/write content products under

  codestable/

  — do not open design.md, modify items.yaml, or create feature directories. These are tasks for sub-skills
• Do not make decisions on behalf of sub-skills — e.g., do not perform brainstorm triage in this skill (that's

  cs-brainstorm

  's job), do not judge which mode cs-arch should use in this skill
• Do not recommend multiple skills at once — only point to one path each time. If the user has two independent requests, split into two rounds: finish A first then return to B
• Do not repeat details of the system overview —

  codestable/reference/system-overview.md

  (exists after onboarding) is the authoritative full version; this skill only provides a concise overview
• Do not bypass

  cs-onboard

  — if the repository is not integrated, onboard first, do not attempt to route directly to downstream skills