context-driven-development

To standardize context frontmatter across a repository, apply a canonical schema that enforces consistent naming, indexing rules, and validation for all context-driven development documents. This ensures contexts remain discoverable and verifiable across projects.

Context-driven development uses a frontmatter-driven contract to define outcomes, validate progress, and keep project knowledge aligned. It centralizes context creation, updates, and synchronization to maintain a verifiable and reusable project index.

Create and update context indices by running context-create or context-update commands. This generates and refreshes context documents and their associated index documentation while enforcing a consistent structure for feature tracking.

Yes, you can use wrapper skills for cross-project integration. The canonical context standard guides wrapper skills and documents integration expectations without exposing the underlying implementation details of the context management system.

No external dependencies are required to validate documentation. The context-driven development standard operates independently to enforce frontmatter schemas and index structures, ensuring consistent validation and search across the repository.

The best way to maintain searchable context indices is to automate context planning and synchronization using a canonical standard. Enforcing consistent indexing rules and operational guidance keeps contexts discoverable and reusable across the repository.