enrich-capabilities

Merge KB capability definitions with project-profile overrides into enriched-capabilities YAML.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents downstream planning from using generic capability definitions by producing a single, project-ready enriched capability record that merges the KB baseline with project-profile overrides and constraint-aware depth selection.

Core Features & Use Cases

  • Capability enrichment by merging KB depth-spectrum business rules, success criteria, failure scenarios, and experiential warnings with project-profile context.
  • Depth selection with cross-tree depth caps and security/compliance ratcheting that enforces stricter rules when profile requirements demand it.
  • Decision surfacing support by emitting a decision-manifest that records key inferred decisions (including ratchet selection) with grounding tier and alternatives for user review.

Quick Start

Run enrich-capabilities during the product-keeper specify stage 4 by providing scope.yaml, a frozen project profile YAML, and the domain knowledge taxonomy path, then write the enriched-capabilities output to your requested .garura product path.

Frequently Asked Questions about enrich-capabilities

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

FAQPage Schema
How do I enrich enterprise capability definitions with project-specific profile overrides?

To enrich enterprise capability definitions, merge KB baseline business rules with a frozen project profile YAML to generate an enriched-capabilities YAML. This ensures downstream intent-epic generation uses constraint-aware depth selection instead of generic definitions.

How does security ratcheting work when applying compliance rules to capability selection?

Security ratcheting enforces stricter compliance rules during capability selection when project profile requirements demand it. The mechanism records all ratchet selections and inferred decisions in a decision-manifest.yaml with grounding tiers and alternatives for review.

How do I generate a decision manifest for inferred capability rules?

Generate a decision manifest by running capability enrichment with selective KB block reads via grep and a frozen project profile. The process emits a decision-manifest.yaml recording key inferred decisions, grounding tiers, and alternatives while strictly avoiding inventing business rules.

What is the best way to reconcile depth constraints with profile context during specify-stage planning?

Reconcile depth constraints with profile context by applying cross-tree depth caps and security ratcheting to KB-defined capabilities. This produces a project-ready enriched capability record merging the KB baseline with profile-specific overrides for downstream planning.

Can I use YAML generation for intent-epic planning without inventing business rules?

Yes, YAML generation for intent-epic planning strictly requires grounding in KB, profile, and brief sources only. The enrichment process performs selective KB reads via grep and detects missing KB sources to prevent any invention of business rules beyond provided inputs.

Why does downstream planning fail when using generic capability definitions instead of enriched ones?

Downstream planning fails with generic definitions because they lack project-profile context, numeric success criteria grounding, and constraint-aware depth selection. Enriching capabilities prevents this by merging KB baselines with profile overrides into a single project-ready record.