excavate-synthesis

You can synthesize multi-source findings into structured specs by merging raw source analysis, architecture analysis, and API extraction outputs into a single cohesive synthesis artifact with provenance citations.

The best way to resolve conflicts in multi-source architecture analysis is applying a defined hierarchy to disagreements while recording both viewpoints, ensuring the final synthesis document maintains accurate multi-source corroboration.

Generating reimplementation essentials from raw source analysis involves running a phase-driven workflow that merges independent outputs into domain-ready behavioral summaries and a dedicated reimplementation-essentials draft.

Yes, you can use architecture analysis and API extraction outputs to create cross-reference reports, as the Skill processes these independent analysis outputs to produce cross-reference reporting and coverage gaps.

Yes, you need independent analysis outputs such as feature discovery, architecture analysis, or API extraction before starting multi-source synthesis, as the Skill merges these existing outputs into a consolidated synthesis bundle.

Synthesizing multi-source findings without provenance citations limits traceability and conflict resolution, making it difficult to track coverage gaps or record disagreements through a defined hierarchy during reimplementation.