aggregate-decode-proposals

Aggregate per-unit decode proposals into a deterministic proposals.yaml index.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates the manual effort of stitching together extracted specs, test results, and citation integrity checks into a single, promotion-ready proposals.yaml artifact.

Core Features & Use Cases

  • Deterministic master proposals aggregation: Walks the /decode proposals tree for behaviors, flows, and aspects and emits a unified proposals.yaml index.
  • Test outcome and citation-integrity joining: Associates each unit with its test-run report and citation-integrity report, and computes baseline_green deterministically.
  • Tier classification for enrichment vs addition: Resolves Tier 2 vs Tier 3 by checking whether matching entries already exist in product LTM (and features.yaml for prior codify runs), then outputs correct targets for /garura:enrich.

Quick Start

Run aggregate-decode-proposals with the decoded proposals root, the test-run reports directory, the citation-integrity reports directory, the resolved features.yaml path, the product base path, and the output path to generate proposals.yaml for promotion to product LTM.

Frequently Asked Questions about aggregate-decode-proposals

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

FAQPage Schema
How do I aggregate decode outputs into a deterministic proposals.yaml index?

Aggregating decode outputs into a proposals.yaml index requires running the Skill with your decoded proposals root, test-run reports, citation-integrity reports, features.yaml path, and product base path to consolidate per-unit specs and verification artifacts into a master index.

What is baseline_green computation in decode proposal aggregation?

Baseline_green computation is a deterministic process that associates each decoded unit with its test-run report and citation-integrity report. It calculates the verification status to ensure extracted specs are validated before promotion to product LTM.

How do I classify proposals for enrichment versus addition when aggregating decode outputs?

Proposal classification for enrichment versus addition resolves Tier 2 versus Tier 3 by checking whether matching entries already exist in the product LTM and features.yaml. It then outputs correct targets for downstream enrichment operations.

Does proposals.yaml aggregation require citation verification and test execution beforehand?

Yes, proposals.yaml aggregation requires prior decode extraction, specification, test generation, execution, and citation verification. The Skill joins these completed test-run and citation-integrity reports with per-unit behavioral, flow, and aspect specs.

Why does decode proposal aggregation fail when tier resolution cannot be established?

Decode proposal aggregation implements strict failure reporting when tier resolution cannot be established or reports are missing. This prevents incomplete or unverified specifications from being promoted into the product LTM via the proposals.yaml index.