garura:enrich

Promote approved taxonomy-tagged issue proposals into product LTM and ADR archives.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It provides a safe, reviewer-controlled terminal step that converts tiered, taxonomy-tagged proposals from issue STM into outward-facing product LTM and optionally new ADRs, then archives the processed issue so it is not re-applied.

Core Features & Use Cases

  • Normalizes native extractor proposals into a reconciliation format suitable for review without modifying the original source proposals.
  • Reviewer approval checkpoint by tier: forces explicit per-entry approval for Tier 1 while using batch-with-diff defaults for Tier 2 and Tier 3.
  • Applies only approved changes to product LTM and promotes approved Tier 1 ADR drafts into the ADR archive with sequential numbering.
  • Ensures idempotency via archival by moving the entire issue STM into the archived subtree after confirmed successful writes.
  • Runs single-issue or sweep mode to process one issue id or all active issue directories, while excluding archived and pending subtrees.

Quick Start

Use the garura:enrich skill to enrich learning proposals for a specific issue by running: /garura:enrich <issue>.

Frequently Asked Questions about garura:enrich

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

FAQPage Schema
How do I promote taxonomy-tagged proposals into approved product LTM artifacts?

Promoting taxonomy-tagged proposals into product LTM requires a terminal enrichment stage that enforces tier-based reviewer checkpoints, applying only explicitly approved changes to the long-term memory artifacts.

How does tiered approval work for ADR promotion and issue archival?

Tiered approval for ADR promotion forces explicit per-entry approval for Tier 1 entries, while using batch-with-diff defaults for Tier 2 and Tier 3, ensuring only confirmed successful writes trigger STM archival.

How do I process multiple issue STM directories in a single sweep mode run?

Processing multiple directories in sweep mode runs the enrichment stage across all active issue directories simultaneously, automatically excluding archived and pending subtrees from the promotion pipeline.

Why does issue STM archival matter for idempotency in a learning pipeline?

Issue STM archival ensures idempotency by moving the entire processed issue into an archived subtree after confirmed successful writes, preventing the same proposals from being re-applied downstream.

Can I use native proposal sources from distill, reap, codify, or decode directories?

You can use native proposal sources from distill, reap, codify, or decode evidence directories because the enrichment process normalizes them into a reconciliation format suitable for review without modifying the original source proposals.

What happens if taxonomy completeness validation fails during LTM enrichment?

If taxonomy completeness validation fails during LTM enrichment, strict write-boundary roots and approval completeness gating block the process, preventing unverified proposals from being promoted to product LTM artifacts.