What problem does it solve? When running OpenSpec change workflows (explore, propose, apply, archive, android-bug), agents lack access to the project's accumulated design decisions, business rules, and historical bug patterns, leading to proposals that violate existing constraints and fixes that reintroduce old defects. ## Core Features & Use Cases - Stage-by-stage knowledge enrichment: Injects CodeKB semantic search, conventions, and symbol explanations into each OpenSpec stage, from exploration overviews to constraint association during proposals. - Archive knowledge feedback: Distills new design decisions and rules from completed changes via codekb extract --from-change, marking superseded entries and maintaining traceability with source_change. - Bug pattern retrieval: Surfaces known_issues and historical defect patterns on suspect symbols during Android bug investigation so fixes do not reintroduce past failures. - Use Case: While drafting a proposal for a payment module change, the agent queries CodeKB for decisions and rules scoped to that module, discovers the constraint that amounts must use BigDecimal, and adds a "相关约束" section referencing the knowledge entry IDs. ## Quick Start Ask the agent to enrich the current OpenSpec proposal with relevant CodeKB design decisions and conventions for the affected module.
