understanding-specs

To ingest and validate a spec hierarchy, provide the full work item path. The skill reads required documents across product, capability, feature, and story levels, then generates a structured context summary for implementation.

When critical specification files are missing, the context loading process aborts. It provides actionable guidance to help you locate or create the necessary documents before proceeding with the work item.

Yes, you can generate context from existing PRD and TRD documents. The skill reads these enrichments and offers a creation flow to generate corresponding specifications if they are missing from the hierarchy.

You locate a work item within specification levels by passing its hierarchical path. The skill traverses product, capability, feature, and story documents to establish the exact location and architectural constraints.

Loading ADRs is necessary when validating specifications to establish architectural constraints. Reading Architecture Decision Records ensures the generated context summary aligns with existing technical decisions and project guidelines.

Yes, the spec validation process supports hierarchical work item paths. You provide the full nested path, such as capability/feature/story, to accurately ingest and validate the corresponding specification documents.