infer-enriched-capabilities-from-code

Merge domain KB definitions with code scan evidence to emit enriched capability YAML artifacts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It replaces generic capability knowledge with per-capability enrichment that is grounded in what the current codebase actually implements, preventing downstream planning from relying on assumptions during brownfield codify.

Core Features & Use Cases

  • Reverse-engineered capability enrichment: Infers business-rule overrides, depth-spectrum caps, and experiential warnings by merging domain KB base values with project-specific scan evidence.
  • Evidence-grounded decisions: Produces traceable outputs and a decision manifest that links each override and warning to explicit scan-index or KB feature sources.
  • Safe, deterministic artifact production: Writes the enriched-capabilities YAML, decision manifest, and resolution trace under the STM area for use exclusively by the product-keeper during /codify.

Quick Start

Run the infer-enriched-capabilities-from-code skill during the /codify play after infer-scope-from-code, providing scan-index.json plus the upstream codify proposals and an output_path under {stm_base}/{issue}/evidence/codify/proposals/scope/.

Frequently Asked Questions about infer-enriched-capabilities-from-code

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

FAQPage Schema
How do I infer enriched capabilities from an existing codebase during brownfield codify?

Capability inference generates traceable YAML artifacts and decision manifests that link business-rule overrides and warnings to explicit scan-index sources. It validates inputs, enforces depth-cap constraints, and computes caps from code signals for deterministic artifact production.

What inputs are required for capability inference and depth-spectrum cap calculation?

Capability inference requires scan-index.json, upstream codify proposals, and an output path under the STM evidence directory. It applies after infer-scope-from-code during the codify play to validate resolution-protocol requirements and compute depth-spectrum caps from code signals.

Can I use codebase scanning to extract business-rule overrides for downstream intent-epic generation?

Yes, codebase scanning extracts business-rule overrides by merging domain KB base values with project-specific scan evidence. The resulting enriched capability artifacts are required specifically for downstream intent-epic generation during brownfield codify bootstrapping.

How does decision traceability work when reverse-engineering enriched capabilities from code?

Decision traceability works by producing a decision manifest that links each override and warning to explicit scan-index or KB feature sources. This ensures evidence-grounded decisions by validating inputs and emitting traceable YAML artifacts under the STM area for the product-keeper.