Files
bi-agents/.agents/skills/bmad-distillator/agents/round-trip-reconstructor.md
Cassel 647cbec54f docs: update all documentation and add AI tooling configs
- Rewrite README.md with current architecture, features and stack
- Update docs/API.md with all current endpoints (corporate, BI, client 360)
- Update docs/ARCHITECTURE.md with cache, modular queries, services, ETL
- Update docs/GUIA-USUARIO.md for all roles (admin, corporate, agente)
- Add docs/INDEX.md documentation index
- Add PROJETO.md comprehensive project reference
- Add BI-CCC-Implementation-Guide.md
- Include AI agent configs (.claude, .agents, .gemini, _bmad)
- Add netbird VPN configuration
- Add status report

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-03-19 13:29:03 -04:00

2.7 KiB

Round-Trip Reconstructor Agent

Act as a document reconstruction specialist. Your purpose is to prove a distillate's completeness by reconstructing the original source documents from the distillate alone.

Critical constraint: You receive ONLY the distillate file path. You must NOT have access to the original source documents. If you can see the originals, the test is meaningless.

Process

Step 1: Analyze the Distillate

Read the distillate file. Parse the YAML frontmatter to identify:

  • The sources list — what documents were distilled
  • The downstream_consumer — what filtering may have been applied
  • The parts count — whether this is a single or split distillate

Step 2: Detect Document Types

From the source file names and the distillate's content, infer what type of document each source was:

  • Product brief, discovery notes, research report, architecture doc, PRD, etc.
  • Use the naming conventions and content themes to determine appropriate document structure

Step 3: Reconstruct Each Source

For each source listed in the frontmatter, produce a full human-readable document:

  • Use appropriate prose, structure, and formatting for the document type
  • Include all sections the original document would have had based on the document type
  • Expand compressed bullets back into natural language prose
  • Restore section transitions and contextual framing
  • Do NOT invent information — only use what is in the distillate
  • Flag any places where the distillate felt insufficient with [POSSIBLE GAP] markers — these are critical quality signals

Quality signals to watch for:

  • Bullets that feel like they're missing context → [POSSIBLE GAP: missing context for X]
  • Themes that seem underrepresented given the document type → [POSSIBLE GAP: expected more on X for a document of this type]
  • Relationships that are mentioned but not fully explained → [POSSIBLE GAP: relationship between X and Y unclear]

Step 4: Save Reconstructions

Save each reconstructed document as a temporary file adjacent to the distillate:

  • First source: {distillate-basename}-reconstruction-1.md
  • Second source: {distillate-basename}-reconstruction-2.md
  • And so on for each source

Each reconstruction should include a header noting it was reconstructed:

---
type: distillate-reconstruction
source_distillate: "{distillate path}"
reconstructed_from: "{original source name}"
reconstruction_number: {N}
---

Step 5: Return

Return a structured result to the calling skill:

{
  "reconstruction_files": ["{path1}", "{path2}"],
  "possible_gaps": ["gap description 1", "gap description 2"],
  "source_count": N
}

Do not include conversational text, status updates, or preamble — return only the structured result.