manage-features

Generate a canonical domain-capability-feature catalog from enriched capabilities YAML.

3|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/kapilvirenahuja/garura --skill manage-features-kapilvirenahuja
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: manage-features
Source: https://github.com/kapilvirenahuja/garura/tree/main/core/components/skills/manage-features
Command: npx skills add https://github.com/kapilvirenahuja/garura --skill manage-features-kapilvirenahuja

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The manage-features Skill turns enriched capability data into a stable, canonical 3-tier feature catalog so downstream specification and epic generation can reliably cross-check product features and status.

Core Features & Use Cases

  • Authors a canonical feature catalog: Generates .garura/product/scope/features.yaml from enriched-capabilities.yaml using a strict domain → capability → feature hierarchy.
  • Applies deterministic status rules: Uses greenfield defaults or brownfield override-and-infer logic with the 5-point status vocabulary (planned | development | rollout | released | cleanup).
  • Emits a decision manifest for traceability: Writes a decision-manifest YAML that records inferred statuses, grounding sources, and tier information for the orchestrator’s tiered surfacing flow.
  • Enforces authoring rules from LTM: Loads feature-catalog rules from the provided LTM path and applies them to ensure structural validity and consistent output.

Quick Start

Ask the system to run manage-features during specify Stage 4b by providing enriched_capabilities_path, project_profile_path, stm_output_base, and ltm_rules_feature_catalog_path.

Frequently Asked Questions about manage-features

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

FAQPage Schema
How do I generate a canonical product feature catalog from enriched capabilities?

To generate a product feature catalog, you use enriched-capabilities.yaml and a project profile to create a strict 3-tier domain, capability, and feature hierarchy written to features.yaml during the specify Stage 4b workflow.

What is the 3-tier taxonomy used for structuring enterprise product specifications?

The 3-tier taxonomy structures enterprise product specifications into a strict domain, capability, and feature hierarchy, enabling reliable cross-checking of product features and statuses for downstream epic generation.

How does status inference work for a brownfield enterprise SDLC feature catalog?

Status inference for a brownfield feature catalog applies override-and-infer logic using a 5-point vocabulary of planned, development, rollout, released, and cleanup, recording grounding sources and tier information in a decision manifest.

Can I enforce custom LTM rules when authoring a feature catalog?

You can enforce custom LTM feature-catalog rules by providing the ltm_rules_feature_catalog_path, which the Skill loads to validate the structural validity and ensure consistent output of the generated features.yaml file.

What is the best way to track inferred feature statuses for downstream specification?

The best way to track inferred statuses is by emitting a companion decision manifest YAML that records inferred statuses, grounding sources, and tier information, enabling the orchestrator's tiered surfacing flow for traceability.

What inputs do I need to provide to run the manage-features workflow?

You need to provide the enriched_capabilities_path, project_profile_path, stm_output_base, and ltm_rules_feature_catalog_path to execute the workflow and write artifacts to the specified output base paths.