epic-grooming

To fix orphaned epics in your project taxonomy, you can scan momentum artifacts to identify unmapped epics, propose mapping them to registered definitions or creating new ones, and reassign stories after explicit approval. Updates are then applied to epics.md.

The best way to reassign stories across different epics is to use momentum-tools epic-membership functionality, which applies story reassignment systematically while ensuring all architectural context and FR/NFR coverage changes are recorded in completion notes.

Epic grooming handles story slugs and FR/NFR coverage by applying systematic analysis across momentum artifacts to detect gaps, ensuring every story maintains proper functional and non-functional requirements alignment before any taxonomy mutations are proposed.

Yes, you need explicit developer approval before updating epic definitions because the workflow is proposal-driven; it generates merge, create, or split proposals with rationale and awaits direct confirmation before mutating epics.md or reassigning any stories.

You should use an epic grooming workflow for taxonomy harmonization when your project has accumulated orphaned slugs and misaligned stories across momentum artifacts, requiring structured discovery and proposal-driven governance to restore navigability.

No, you cannot update epics.md templates automatically without manual review; the workflow requires explicit developer approval before applying any template updates or story reassignments to ensure all taxonomy changes remain traceable and governed.