skf-refine-architecture

Architecture documentation gap detection identifies undocumented integration paths between skills with compatible APIs. By processing original architecture docs and generated skill inventories, it ensures no hidden connectivity is missed and automatically fills these integration gaps.

Architecture document contradictions occur when planned capabilities mismatch actual skill API surfaces, such as protocol mismatches or missing bridge layers. Issue flagging highlights these discrepancies with evidence-backed corrections citing specific skill exports, types, and protocols.

Refining architecture docs with verified skill API evidence involves enforcing citation of specific skill exports, types, and protocols for all findings. This process preserves all original architecture content while producing compliant, fully documented refined architectures.

Yes, you can flag missing FFI bridge layers between Rust and TypeScript library integrations. The refinement process detects omitted bridge layers, cites relevant APIs from both skills, and proposes a compliant integration path to resolve the contradiction.

Surfacing unused capabilities and cross-library synergies from skill APIs is achieved through improvement suggestions. This technique strengthens the architecture by identifying untapped feature opportunities without altering the original architecture content.

To generate a refined architecture document, you need to provide the file path to your original architecture document. You can also optionally supply a VS feasibility report to ensure the refinement process incorporates verified feasibility findings.