understanding-spx

To load hierarchical context, provide a full work item path to ingest product, capability, feature, and story specifications. The skill validates required documents, reads optional PRDs and ADRs, and outputs a structured summary to guide implementation.

When required specifications are missing or ambiguous, the context ingestion aborts early and provides actionable remediation steps. It also prompts for spec creation if a PRD exists but the corresponding specification document is missing.

Yes, you can read ADRs and PRDs alongside capability and feature specs. The context loader automatically detects and reads these optional documents when present, including ADR references in the final structured context summary.

You verify required documents by running the context loader against a work item path. It checks for the presence of mandatory product guides and capability specs, aborting with actionable guidance if any required document is missing.

The best way to ingest complete CODE framework context is using a full hierarchical work item path. This reads across product, capability, feature, and story levels, validating dependencies and outputting a structured summary with document counts and ADR references.

The work item path should follow a hierarchical format like 10-cli.capability/20-commands.feature/30-build.story. This structured path enables the loader to traverse and ingest specifications across product, capability, feature, and story levels accurately.