manage-architecture

Mapping project architecture involves merging derived module data with LLM-enriched annotations. This coordinates discovery and persistence across multi-module projects to produce a structured representation for downstream planning.

LLM enrichment analyzes documentation and code to assign module responsibility, purpose, dependencies, and skills. It transforms raw project data into a structured architectural view and persists enriched data to llm-enriched.json for downstream consumption.

Yes, you need local data exports under .plan/project-architecture. Specifically, derived-data.json and llm-enriched.json are required to execute the documented workflow for discovering and enriching your project architecture.

Yes, architecture discovery supports multi-repo and multi-module projects. It collects raw module data from extensions to automatically generate a solution-outline-ready representation for module placement decisions.

Automating raw project data transformation requires executing a documented workflow of discovery, enrichment, and persistence. This merges derived module data with LLM annotations to persist a structured architectural view for planning and execution.

Architecture enrichment requires strict script execution to coordinate discovery and persistence across multiple modules accurately. It enforces the documented workflow to ensure derived data and LLM annotations merge correctly into the structured representation.