multi-lane-report-assembly

Merges parallel research lane outputs into one evidence-graded findings report.

2|Updated Jul 18, 2026
One-click install
npx skills add https://github.com/Arasz/ai-badger --skill multi-lane-report-assembly-arasz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: multi-lane-report-assembly
Source: https://github.com/Arasz/ai-badger/tree/main/features/common/skills/multi-lane-report-assembly
Command: npx skills add https://github.com/Arasz/ai-badger --skill multi-lane-report-assembly-arasz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? When you fan out 2+ parallel research or review lanes, each returns its own finding blocks, and merging them by hand produces truncated claims, broken cross-references, duplicated findings, and reports that fail strict renderers. This Skill defines the lane output contract and the exact assembly procedure to produce one clean, evidence-graded record. ## Core Features & Use Cases - Verbatim block extraction and truncation: Lifts ### F# — claim [GRADE] blocks from authoritative full summaries (never truncated delegation transcripts) and cuts each block at embedded ## Still open headers so the renderer captures all findings. - Consolidation and renumbering: Dedupes cross-cutting findings into a single section with provenance notes, moves ACCEPTED items to a register, renumbers sequentially, and runs a stale cross-reference pass. - Render-gated verification: Uses the renderer as a format gate that refuses ungraded claims and READ/MEASURED findings without Evidence lines, plus a checklist covering grade mix, severity counts, and section structure. - Use Case: After dispatching three parallel security review lanes via Hermes, pull the full summaries from the Hermes state DB, merge 41 findings into one report, renumber them, and render to a temp directory to confirm the provenance chart counts every finding. ## Quick Start Assemble the findings from my three parallel review lanes into a single evidence-graded report and verify it renders cleanly.

Frequently Asked Questions about multi-lane-report-assembly

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

FAQPage Schema
How do I merge findings from multiple parallel research agents into one report?

Extract each lane's `### F# — claim [GRADE]` blocks from the full summaries, truncate each block at its embedded `## Still open` header, dedupe cross-cutting findings, renumber sequentially, and fix stale in-body references. Then render the result as a format gate before delivery.

Why does my assembled report only count some of the findings?

Lane files embed their own `## Still open` sections, and when lifted verbatim that header lands inside the last finding's body and ends the renderer's capture early. Strip each block at the first `## ` header before merging so all findings are counted.

How do I get full delegation summaries from Hermes instead of truncated transcripts?

Query the Hermes state DB read-only with sqlite3 against the async_delegations table for your delegation_id. The result_json contains summary_full_path files holding the complete markdown, while live delegation transcripts abbreviate long summaries.

What evidence format should parallel review lanes return?

Each lane should return one `### F# — claim [GRADE]` block per finding with a grade from MEASURED, READ, INFERRED, or UNVERIFIED, plus a required Evidence line with path:line or URL for READ and MEASURED grades, and a Still open list with a grade-mix line.

Why do cross-references break after renumbering findings?

Renumbering invalidates every in-body reference like "see F12" or "F2's settings", including prose forms a plain sed replace misses. Grep the assembled file for every old id with context and map each to the new finding or register id before review.