cascading-specs

To identify missing specifications, you can scan your project for existing documents like vision, requirements, and use cases. This Skill performs a gap analysis to find missing artifacts and recommends what document to create next based on the cascade principle.

The cascade principle is a development process rule where changes flow downward only, ensuring consistency from vision to code. It enforces a traceable hierarchy where vision documents dictate requirements, which then dictate use cases and architecture.

You can check project requirements completeness by auto-discovering existing documents and analyzing gaps. This process scans for entity models, architecture, and tests to identify what is missing and suggests the next document to create.

Yes, this skill auto-discovers existing specifications by scanning for common documents like architecture and tests. It analyzes your development process coverage to ensure consistency and recommends the next steps to fill any identified gaps.

The best way to maintain consistency from vision to code is to enforce a cascade rule where specification changes flow downward only. This ensures that your vision, requirements, use cases, entity models, and architecture remain aligned throughout the development process.

You need specification discovery when starting a new feature to quickly see what requirements exist and identify gaps in use case coverage. It guides you on what to document next to maintain a consistent and traceable development process.