gemini-vault-fusion

Consolidate reverse-engineering documentation into a single vault with source headers.

5|Updated Jun 3, 2026
One-click install
npx skills add https://github.com/rafael-fae/agent-ops-worflow --skill gemini-vault-fusion
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gemini-vault-fusion
Source: https://github.com/rafael-fae/agent-ops-worflow/tree/main/archive/skills/operacao/gemini-vault-fusion
Command: npx skills add https://github.com/rafael-fae/agent-ops-worflow --skill gemini-vault-fusion

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the common failure mode of reverse-engineering documentation workflows where AI-generated summaries look polished but lose critical technical depth, inconsistencies remain hidden, and final deliverables become incomplete or generic.

Core Features & Use Cases

  • Vault consolidation: Merge a large documentation set into a single source file with traceable source headers for review.
  • AI audit and PRD generation: Use a high-reasoning model to detect contradictions, gaps, overlaps, and then draft professional PRD and blueprint structures.
  • Human-AI fusion workflow: Compare the AI output against original docs and rebuild definitive v3.0 documentation that preserves technical detail.
  • Use case: A team finishing a large reverse-engineering effort needs executive-ready documentation without sacrificing schemas, state machines, UX divergences, or implementation waves.

Quick Start

Ask the skill to consolidate the full documentation vault, run an inconsistency audit, and produce fused v3.0 PRD and blueprint drafts that preserve all deep technical details.

Frequently Asked Questions about gemini-vault-fusion

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

FAQPage Schema
How do I consolidate reverse-engineering documentation into a single reviewable vault?

Documentation consolidation merges large reverse-engineering documentation sets into a single source file with traceable source headers. This creates an audit-ready vault where original technical details are preserved for review.

How do I audit AI-generated documentation for contradictions and completeness gaps?

An AI audit uses high-reasoning models to detect contradictions, omissions, and overlaps across consolidated documentation. It identifies completeness gaps to ensure final deliverables maintain technical depth rather than becoming generic summaries.

What is the best way to generate audit-ready PRDs and architectural blueprints from multiple technical documents?

Generating audit-ready PRDs and blueprints involves fusing executive-level summaries with detailed technical references. This workflow rebuilds definitive v3.0 documentation that preserves schemas, state machines, and UX divergences.

Does this documentation audit workflow require structured source attribution?

Yes, structured source attribution is required. The human-AI fusion workflow compares AI output against original docs with traceable source headers to validate consolidation and rebuild definitive technical references.

Why do AI-generated reverse-engineering summaries lose critical technical depth?

AI-generated summaries lose technical depth because inconsistencies remain hidden and final deliverables become incomplete without a validation step. A human-AI fusion workflow compares outputs against original docs to preserve schemas and state machines.