split-specifications

This skill splits a large single-file PRD into a structured directory format to improve navigation and context loading. It automatically generates section-based files like feature contexts and traceability matrices for your monorepo.

The directory structure for organizing product specifications includes an index, product context, non-functional requirements, individual feature files, traceability, and open questions. This structured format replaces the original single-file PRD for better readability.

You need to split a single-file product specification into a directory when it exceeds size thresholds and impacts context loading across teams. This process is essential for monorepo setups or multi-project environments where organized, section-based navigation is required.

When splitting a PRD, the tool handles missing feature codes by slugging the feature name directly from the heading. For example, a heading without a numeric code like 'Signature Display' is automatically converted into a 'signature-display.md' file.

Yes, you can manually invoke the splitting process for a product specification even if it has not hit automatic size thresholds. The skill supports both automatic detection and manual invocation to generate the structured directory and remove the original file.

Splitting a PRD removes the original single-file specifications after successfully generating the structured directory. The skill implements post-split verification and optional cleanup steps to ensure the directory hierarchy is correctly established before deleting the source file.