split-specs

Split Specifications Skill

Converts a single-file product spec ({{specs_dir}}/product_specs.md) into a directory-based format ({{specs_dir}}/product_specs/) for better organization and targeted context loading.

When to Use

• Automatically by design-product and source-product-specs-from-code when the single-file PRD crosses 500 lines or 15 features (feature sections matching ### \d+\.\d+)
• Manually when the user invokes /groundwork:split-specs

Step 0: Resolve Project Context

1. Monorepo check: Does .groundwork.yml exist at the repo root?
   • If yes → Is {{project_name}} non-empty?
     • If empty → Invoke Skill(skill="groundwork:select-project") to select a project, then restart this skill.
     • If set → Project is {{project_name}}, specs at {{specs_dir}}/.
   • If no → Continue (single-project repo).
2. Proceed with the resolved project context.

Step 1: Validate Preconditions

1. Check single file exists: {{specs_dir}}/product_specs.md must exist
   • If missing → output "No single-file PRD found at {{specs_dir}}/product_specs.md. Nothing to split." and stop.
2. Check directory does NOT exist: {{specs_dir}}/product_specs/ must not already exist
   • If it exists → output "PRD is already in directory format at {{specs_dir}}/product_specs/. Nothing to do." and stop.
3. Read the file and count lines and features (sections matching ^### \d+\.\d+).

Step 2: Split the File

Parse the single-file PRD into sections and write each to its own file under {{specs_dir}}/product_specs/.

Directory Structure

{{specs_dir}}/product_specs/
├── _index.md              # Header, metadata, and section 0 (EARS cheat sheet)
├── 01-product-context.md  # Section 1: Product context
├── 02-non-functional.md   # Section 2: Non-functional & cross-cutting requirements
├── 03-features/           # Section 3: One file per feature
│   ├── _index.md          # Section 3 header ("## 3) Feature list (living backlog)")
│   └── <feature-code>.md  # e.g., PRD-SRCH.md, PRD-AUTH.md
├── 04-traceability.md     # Section 4: Traceability
└── 05-open-questions.md   # Section 5: Open questions log