frd-split

To split a large Feature Requirements Document, you apply a parent-delivers-value hierarchy to break it down. This ensures each feature unit is cohesive, independently planable, and correctly scoped, preventing documentation sprawl.

The parent-delivers-value rule is a hierarchy enforcement mechanism for Feature Requirements Documents. It ensures parent files act as umbrella documents while automatically scaffolding child FRDs with correct prefixes to maintain logical feature boundaries.

You should restructure your FRD to merge or nest requirements when the document grows too large or contains multiple distinct features. This creates a clean, modular structure that is easier for engineering teams to plan and implement.

Validating requirement coverage and prefix uniqueness across a project directory involves operating on project-specific FRD files. This ensures each feature unit maintains correct scoping and prevents duplicate prefixes during the restructuring process.

Feature scoping operates directly on project-specific FRD files to restructure them. You need an existing target FRD file within your project directory structure to apply the appropriate split, merge, or nest operations.

The best way to prevent documentation sprawl is enforcing a strict parent-delivers-value hierarchy within your FRDs. This resolves bloated requirements by ensuring each feature unit remains independently manageable and correctly scoped.