What problem does it solve?
It reduces context rot and missing coverage by turning a repository’s code and relevant external resources into structured, discoverable component and external specs you can reuse across future deliveries.
Core Features & Use Cases
- Repo component indexing: Scans controllers/services/models/helpers/migrations (configurable via arguments) and generates component spec files under
specs/.index/components/.
- Topology + routing guardrails: Builds a project topology snapshot to decide what to index and can halt early when required roots are missing.
- External documentation & tool capture: Fetches and documents external URLs and also documents MCP resources or other plugin skills into
specs/.index/external/.
- Change-aware and safe re-runs: Supports
--dry-run, --changed, and content-hash skipping to avoid unnecessary rewrites.
Quick Start
Run the indexing workflow for your repo by calling /curdx-flow:index with the options you want, such as limiting the scan to src and skipping deep interviews.