ndx-reshape

Restructuring a PRD hierarchy involves identifying structural problems like excessive epics and proposing a cleaned target structure. This Skill groups related epics into a manageable set of 7-12 top-level items, adjusting levels and reparenting scattered features for clarity.

Reorganizing overlapping PRD features and orphaned tasks is handled by detecting structural issues and proposing a cleaned target structure. It merges overlapping domains, reparents orphaned items, and executes the changes using MCP tools like move_item and merge_items.

Merging features and reparenting tasks in a large PRD is supported safely through guided restructuring. The process uses MCP tools including merge_items and reorganize, then verifies the updated structure with get_prd_status and a final git commit workflow to ensure integrity.

A well-structured PRD hierarchy should contain approximately 7-12 top-level epics. Each top-level epic groups 3-15 features, and each feature contains 2-10 tasks, creating a clean, manageable product specification hierarchy.

To start restructuring your product specification, you need to provide the current PRD structure. The Skill then analyzes the existing epics, features, and tasks to propose a cleaned target hierarchy and performs the reorganization.

PRD reorganization handles incorrect level assignments by identifying features that should be tasks or vice versa. It executes level adjustments using MCP tools like edit_item and move_item, ensuring each item sits at the correct hierarchical depth within the target structure.