infer-features-from-code

Infer a 3-tier domain feature catalog from scan-index.json code artifacts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns existing codebases into a canonical 3-tier feature catalog (domain → capability → feature) by scanning structure, routing, and wiring, then assigning a practical lifecycle status to each feature.

Core Features & Use Cases

  • Feature catalog inference from scan artifacts: Builds scope/features.yaml by reading scan-index.json and enumerating modules, routes/handlers, and entry-point wiring for each capability.
  • Release lifecycle status heuristics: Assigns one of planned, development, rollout, released, or cleanup per feature using evidence like deprecation markers, recent git tags, test signals, and churn.
  • Decision traceability for downstream surfacing: Produces resolution traces and status inference manifests for auditability and later stages in the AI-Native SDLC.

Quick Start

Ask product-keeper to run infer-features-from-code during /codify with the required paths so it generates scope/features.yaml at the codify proposals scope.

Frequently Asked Questions about infer-features-from-code

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

FAQPage Schema
How do I generate a feature catalog from existing source code?

You generate a feature catalog from existing code by scanning modules, routes, and entry-point wiring using a scan-index.json file. This process produces a canonical 3-tier domain capability catalog with evidence-backed feature candidates.

How do I infer release status for features from code repositories?

Infer release status for features by applying heuristics based on deprecation tags, recent git tags, test presence, and code churn. This assigns lifecycle statuses like planned, development, rollout, released, or cleanup to each inferred feature.

What is a 3-tier domain capability feature catalog?

A 3-tier domain capability feature catalog is a hierarchical structure mapping domain to capability to feature. It is built by enumerating existing code modules and routing to provide evidence-backed feature candidates for deterministic planning.

Does feature inference from code require specific input formats?

Feature inference requires YAML input contracts and a valid scan-index.json file to enumerate code structure. These inputs allow the system to apply status inference heuristics and output updated feature artifacts plus manifests.

How do I track decision traceability for inferred software features?

Track decision traceability for inferred features by generating resolution traces and status inference manifests during the codify process. These artifacts provide auditability for downstream stages in the AI-native software development lifecycle.

When should I run feature inference during the codify process?

Run feature inference during the codify process after domains and enriched capabilities are proposed. Applying it at this stage ensures the generated scope/features.yaml contains accurate, evidence-backed feature candidates for enterprise planning.