Owner direction: the README speaks to a first-time user of today's
CodeStable, not to its history or internal methodology.
- Removed the 'build -> evaluate loop' chapter (maintainer methodology;
lives in the repo, not the front page) and its tagline pointer
- v1 is now mentioned exactly once per language — inside the Upgrade
section, which also gained a line assuring that legacy knowledge
(compound/, features/, old tools) stays covered by v2 retrieval
- Design / catalog / workflow / roadmap sections rewritten to describe
what CodeStable is, not what it used to be; alias line reduced to
'cs-code-review is an alias of cs-review'
Doc contract suite stays green (96 passed).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Rebuilt the three v2 content sections as the main narrative instead of
v1-era framing with patches:
- 'Design: thin harness, thick context' — write responsibilities not
steps; the hard-gate table per flow (incl. 3-round review cap, design
persistence, test-first); on-demand references for engineering
judgment; the six homes of knowledge with graduate-before-delete
- Skill catalog refreshed (cs-review three modes, epic inline-first
sub-designs, the single cs-code-review alias called out)
- 'Workflow and project memory' — one execution mainline, per-request
risk judgment, zero artifacts for ordinary work, retrieval-with-source
discipline, zero-migration v1 boundary
- Tagline gains the one-line methodology; roadmap logs the dogfood loop
Personal narrative sections (origin, orchestration comparison,
philosophy, build->evaluate loop) preserved as-is. Doc contract tests
stay green (96 passed).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Dogfood feedback: work/ entries like paseo-native-session-bridge.md give
no clue whether they are a feature, issue, or epic when it is time to
compress them. Two rules, zero new mechanism:
- work docs are named with a type prefix (feat-/issue-/refactor-/epic-),
so ls classifies and wrap-up knows the destination per type
- epic sub-designs are inline-first: a few lines under the item entry;
only risk-escalated items get their own work/feat-{slug}.md, carrying
'epic: {slug}' frontmatter with a backlink from the epic item row —
flat files with two-way pointers, no subdirectories. Epic wrap-up now
also sweeps its sub-item work docs.
Docs (WORKFLOW/README zh+en) synced. 96 passed.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The skill has outgrown its name — it reviews designs and runs repo audits,
not only code. cs-review is the canonical entry; cs-code-review ships as
the one thin forwarding alias (the explicit exception to the no-shim rule,
kept for the carried-over v1 habit). References in cs / cs-feat / cs-epic /
cs-issue / cs-refactor, the Codex agent config, both contract-test skill
sets (V2_SKILLS + SHIM_SKILLS), and all public docs / CHANGELOG / ADR-004
updated. Also refreshed the leftover v1 openai.yaml wording. 96 passed.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Dogfood feedback (session 001c553b): calling cs with a concrete request
recommended an entry and then waited for the user to re-invoke it — one
confirmation too many. cs now classifies intent: clear action requests
announce the chosen entry in one line and continue executing under that
skill's discipline in the same turn; advice requests still get a
recommendation only; ambiguous requests that would materially change what
happens next get exactly one focused question. Handoff does not widen
authority — the target skill's gates and checkpoints apply unchanged.
Safety anchors and docs (SKILL_CATALOG / WORKFLOW / README zh+en) synced.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Owner practice decision: on risk escalation the proposal is written into
.codestable/work/{slug}.md before independent design review and user
confirmation — the design trail is always on disk for high-risk work.
Contract anchor added; wrap-up section reconciled (high-risk work docs
are created at design alignment, others on cross-session/handoff need).
Sync WORKFLOW / README (zh+en).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
- work doc gains a status-and-open-items section so cross-session resume
has a defined landing spot for pending confirmations (recovery contract)
- cs-code-review: reviewer dispatch requires a self-contained context
packet (intent, scope, exclusions, expected graded findings); main flow
owns integration and final verdict (collaboration contract)
- cs-onboard: gitignored .codestable stops with a report instead of
silently proceeding (failure behavior)
- Sync WORKFLOW / README (zh+en)
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
- cs-code-review: add design review mode; cap blocking fix-and-rereview at
2 rounds, then escalate to human arbitration with the disagreement
- cs-feat: risk-escalated designs pass independent design review before user
confirmation; test-first when a test setup exists; completed changes get
independent review by default (trivial edits may skip)
- cs-epic: decomposition passes independent design review before user confirmation
- cs-issue / cs-refactor: independent review by default, trivial changes may skip
- Sync WORKFLOW / SKILL_CATALOG / README (zh+en)
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
- Removed unnecessary compiled Python files from __pycache__.
- Updated `search-yaml.py` to enhance filter syntax and usage examples, including support for OR logic in filters.
- Revised multiple SKILL.md files to clarify instructions, emphasizing the importance of reading `.codestable/attention.md` before proceeding with actions.
- Adjusted paths in documentation to consistently reference `.codestable/` instead of `codestable/`.
- Enhanced descriptions in requirement and roadmap documentation to better define the purpose and structure of each component.
- Improved clarity in the `cs-trick` documentation regarding the nature of the reference library and its usage.
- Ensured all references to tools and commands are consistent with the new directory structure.
- Introduced a new skill 'cs' as the unified entry point for CodeStable, providing an overview of the system and routing user requests to appropriate sub-skills.
- Updated README.md to include usage instructions for the new root entry command.
- Enhanced documentation in various skills (cs-roadmap, cs-feat-design, cs-onboard) to clarify the role of the 'cs' skill and its interactions with other components.
- Improved clarity on the roadmap structure, emphasizing the importance of architectural planning and interface contracts.
- Added detailed sections for module splitting and interface contracts in the roadmap documentation.
- Updated SKILL.md files to reflect new naming conventions and project structure.
- Changed references from easysdd to codestable in various documentation files.
- Adjusted paths for requirements, roadmap, and tricks to align with the new structure.
- Ensured consistency across all related documents and references.
- Introduced `easysdd-roadmap` skill to manage large feature requests by breaking them down into sub-features with dependencies and statuses.
- Created `SKILL.md` to outline the purpose, usage scenarios, and workflow of the `easysdd-roadmap` skill.
- Added a reference template in `reference.md` for the main document and items.yaml format used in the roadmap.
- Established a clear directory structure for organizing roadmap documents and their associated items.
- Defined rules for single target management, dependency handling, and validation processes to ensure clarity and consistency in roadmap creation.
- Updated all references in SKILL.md files across easysdd-feature-implement, easysdd-feature, easysdd-issue-analyze, easysdd-issue-fix, easysdd-issue-report, easysdd-issue, easysdd-learning, easysdd-onboarding to replace 'design.md', 'checklist.yaml', 'report.md', 'analysis.md', and 'fix-note.md' with '{slug}-design.md', '{slug}-checklist.yaml', '{slug}-report.md', '{slug}-analysis.md', and '{slug}-fix-note.md' respectively.
- Ensured that all documentation reflects the new naming conventions for better clarity and organization.
- Adjusted validation scripts and templates to accommodate the new file naming structure.
- Updated the name and description in SKILL.md to reflect the new focus on learning documentation.
- Adjusted references throughout the onboarding process to point to the new easysdd/compound directory for learning resources.
- Modified the search tools and commands to align with the new directory structure and naming conventions.
- Ensured all relevant documentation templates and examples are updated to use the new naming scheme.
- Enhanced clarity on the purpose of each document type within the easysdd framework.
- Introduced the main easysdd skill to guide users through workflow scenarios.
- Created sub-skills for feature development, issue resolution, knowledge retention, and auxiliary tools.
- Established a structured reference directory for shared conventions, tools, and maintainer notes.
- Defined clear routing for various scenarios to appropriate sub-skills.
- Documented guidelines for maintaining and extending the easysdd skill family.
dafang