infer-research-from-code

Generate domain-scoped research Markdown files from scan-index.json evidence and domain KB.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns scan-derived codebase evidence into per-domain product-scoped research documents, so teams can move forward with deterministic discovery and avoid blank or speculative research when there is no prior product knowledge.

Core Features & Use Cases

  • Evidence-grounded research generation: Creates research/{domain}.md for each selected domain using scan-index.json evidence tied to that domain.
  • Canonical KB extension with explicit gaps: Inherits the five KB-extension sections from the domain KB when available, and marks missing evidence with inline knowledge_gap indicators instead of fabricating content.
  • Resolution trace and decision surfacing: Produces a decision manifest and a resolution trace so inferences and knowledge gaps are auditable and recoverable by later enrichment workflows.
  • Aligned with codify codification flow: Runs strictly after domain-selection inference and emits artifacts into the STM evidence path for downstream promotion.

Quick Start

Run the skill during the codify stage for a given issue, providing scan-index.json plus the domain-selection.yaml, and it will output one research/{domain}.md file per selected domain into the codify evidence directory.

Frequently Asked Questions about infer-research-from-code

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

FAQPage Schema
How do I generate domain research from code evidence when there is no prior product knowledge?

Generate domain research from code evidence by using scan-index.json and the canonical domain KB to produce per-domain Markdown files. This deterministic inference prevents speculative content by marking missing evidence with inline knowledge_gap indicators instead of fabricating data.

What is deterministic inference for product codification?

Deterministic inference for product codification is the process of deriving structured domain research from code evidence using explicit inclusion rules. It ensures auditable inference by emitting decision-manifest and resolution-trace artifacts alongside the generated Markdown files.

How do I document knowledge gaps in domain research files?

Document knowledge gaps in domain research files by using inline knowledge_gap markers where code evidence is absent. This approach ensures missing information is explicitly flagged for later enrichment workflows rather than filled with fabricated assumptions.

When should I use code evidence instead of web research for domain discovery?

Use code evidence instead of web research for domain discovery during the codify stage when no web research and no prior product LTM are available. This makes the codebase the primary evidence surface for generating per-domain Markdown research.

Does the codify workflow require a domain-selection file to generate research?

Yes, the codify workflow requires a domain-selection.yaml file to generate research. The process runs strictly after domain-selection inference to produce scoped Markdown files and resolution-trace artifacts in the STM evidence path.

What are the limitations of deriving domain research solely from scan-index.json?

Deriving domain research solely from scan-index.json limits outputs to available code evidence, explicitly marking absent data as knowledge gaps. It cannot fabricate missing domain context and relies on downstream promotion workflows to resolve flagged gaps.