feature-grooming

Synthesize feature candidates from PRDs, epics, and architecture into features.json entries.

Updated Mar 10, 2026
One-click install
npx skills add https://github.com/iamsteveholmes/momentum --skill feature-grooming
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-grooming
Source: https://github.com/iamsteveholmes/momentum/tree/main/skills/momentum/skills/feature-grooming
Command: npx skills add https://github.com/iamsteveholmes/momentum --skill feature-grooming

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Feature grooming enables product teams to discover, analyze, and maintain a value-first features.json that guides development and QA across projects.

Core Features & Use Cases

  • Value-driven discovery: synthesize feature candidates from architecture, PRDs, and epics, with explicit value analyses and system context.
  • Lifecycle management: merge, split, deduplicate, retire features based on evolving architecture and story progress.
  • Use Case: A team bootstraps a coherent features.json that directly maps business value to technical capabilities, improving prioritization and traceability.

Quick Start

Bootstraps the feature grooming workflow and prepares features.json, awaiting developer approval to write the final entries.

Frequently Asked Questions about feature-grooming

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate value-driven features from PRD and architecture artifacts?

Feature grooming automates the discovery of value-driven features by synthesizing candidate entries from your PRD, epics, and architecture. It maps business value directly to technical capabilities and prepares them for developer approval before writing to your features.json file.

What is a features.json file used for in product story management?

A features.json file acts as the single source of truth for product capabilities. Feature grooming maintains this file by structuring entries with multi-paragraph value analysis, system context, feature type, and verifiable acceptance conditions to guide development and QA.

How do I structure feature entries with value analysis and acceptance conditions?

To structure feature entries, the grooming process generates interoperable records that satisfy specific requirements: a multi-paragraph value analysis, system context, a type classification of flow, connection, or quality, and a verifiable acceptance condition for each feature.

Can I merge or retire existing features as architecture evolves?

Yes, feature grooming supports lifecycle management allowing you to merge, split, deduplicate, and retire features. This ensures your features.json stays coherent as your architecture changes and story progress advances across product development.

Do I need existing epics and stories to bootstrap a coherent features.json?

You need architectural and product artifacts like PRDs, epics, and stories to synthesize candidate features. The grooming workflow uses these inputs to bootstrap a coherent features.json that directly maps business value to technical capabilities.