- Added Vision Spec to capture the overarching application vision, allowing users to articulate their desired outcomes and candidate directions.
- Updated Talk mode to facilitate discussions around the Vision, enabling users to clarify and refine their product ideas without immediate pressure to implement.
- Enhanced templates for issues and epics to reference Vision, ensuring alignment between current development and long-term goals.
- Implemented a new directory structure for Vision-related documents, including vision-index and vision-section-index templates.
- Revised existing documentation to reflect the separation of Vision from Project Spec, emphasizing the importance of maintaining distinct boundaries between desired outcomes and current realities.
- Introduced guidelines for using Vision to support user journeys and product capabilities, allowing for a more structured approach to product development.
- Added a new `ui-spec.md` to define principles for UI visual specifications, including when to create visual specs and how to represent UI elements using ASCII wireframes and Mermaid diagrams.
- Updated README files to include sections on how UI specs utilize visuals, emphasizing the importance of visual representation in understanding UI requirements.
- Enhanced various skill references and templates to incorporate UI visual contracts, ensuring that UI changes are documented with appropriate visual aids.
- Implemented checks in the skill repository to ensure compliance with UI visual specification requirements across relevant documents and templates.
- Added implementation-economy guidance in README and translated README.en.md.
- Introduced economy.md to outline principles for maintaining economic implementation.
- Updated various templates to include references to bounded simplifications and upgrade triggers.
- Enhanced the check-skill-repository.py script to validate economy contracts.
- Revised multiple skill references to incorporate new economy principles and ensure clarity on quality objectives.
- Introduced a new quality.md reference document outlining the nine product quality characteristics based on ISO/IEC 25010:2023.
- Updated design, do, explore, talk, and spec documents to incorporate quality goals and commitments, ensuring they are part of the issue lifecycle.
- Modified templates for various issue types (bug, chore, feature, refactor) to include sections for quality objectives, ensuring that quality considerations are explicitly documented and addressed.
- Implemented checks in the skill repository to ensure quality objectives are included in relevant templates and that the quality.md is referenced appropriately.
- Enhanced the overall structure of documentation to emphasize the importance of quality in design decisions and implementation evidence.
- Updated CLAUDE.md and README files to clarify skill independence and documentation structure.
- Removed facts.md template and integrated essential startup rules into AGENTS.md and CLAUDE.md.
- Revised various reference documents to enhance clarity on knowledge management and project specifications.
- Adjusted init_codestable.py script to eliminate facts.md creation and streamline project initialization.
- Introduced user preferences document to emphasize professional user treatment and technical depth.
- Ensured all changes align with the new structure for knowledge artifacts and project documentation.
- Enhanced README.md to clarify the closing rules for issues and the structure of exploratory issue workspaces.
- Updated SKILL.md for cs-close to specify the merging process for exploratory issues and their candidate articles.
- Improved SKILL.md for cs-how-docs to emphasize narrative usage and reader pathways in documentation.
- Revised SKILL.md for cs-plan to clarify the distinction between independent and exploratory issues.
- Modified SKILL.md for cs-spec-explore to detail the exploratory issue lifecycle and the structure of candidate articles.
- Introduced new templates for exploratory articles and indexes to standardize documentation within exploratory issue workspaces.
- Adjusted project spec and section index templates to focus on usage paths and capabilities rather than code structure.
- Enhanced cs-talk SKILL.md to ensure context reuse and effective questioning during discussions.
- Introduced `cs-spec` for maintaining project and epic specifications.
- Added `cs-spec-explore` for creating exploratory issues to investigate project spec gaps.
- Implemented `cs-talk` for clarifying vague ideas and organizing discussions.
- Created `cs-test` for optional test design associated with specific issues.
- Developed `cs` as a navigation skill to guide users on which CodeStable skill to use.
- Added various templates for project specifications, epic specifications, and exploratory issues.
- Implemented a validation script to check plugin package integrity and structure.
- Introduced `cs-spec` skill to handle upstream specification clarifications, allowing for iterative alignment of specs, code context, and blockers.
- Created a new directory structure under `.cs/specs/` to store specification-related documents.
- Updated existing skills (`cs-talk`, `cs-plan`) to reference the new `cs-spec` skill for improved workflow.
- Enhanced documentation across various skills to reflect the new specification handling process, including templates for spec documentation.
- Added new templates for spec findings, changes, flow, glossary, index, plan briefs, questions, and sources to standardize spec documentation.
- Updated `SKILL.md` files to include references to the new `cs-spec` skill and its functionalities.
- Added guidelines for adhering to `cs-how-docs` in various skills to improve document organization and reader navigation.
- Revised descriptions in `cs-design`, `cs-do`, `cs-complain`, `cs-close`, `cs-test`, `cs-wiki`, and `cs-plan` to emphasize the importance of context reuse and clear documentation paths.
- Introduced a new skill `cs-how-docs` to establish principles for organizing documentation as a knowledge space rather than flat content.
- Updated templates for issues and wiki topics to include structured sections for design conclusions, reader paths, and clear problem statements.
- Ensured that all skills now emphasize the need for confirming current versions of documents and facts before proceeding with tasks.
- Updated cs-test and cs SKILL.md files to clarify testing design principles and guidelines.
- Improved organization and clarity in requirements documentation, including new templates for requirements and wiki topics.
- Introduced cs-wiki for automated wiki generation and requirements candidate documentation.
- Added Browser Bridge CLI documentation, including setup instructions and command usage.
- Created new agents for various functionalities including CS Code Design, CS Debug, and CS Talk.
- Established a structured approach for managing wiki questions and requirements drafts.
- 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.
liuzhengdong