generate-design-guidelines

To generate architecture decision records from a project model, you need a ProjectModel JSON file and an orchestrator tool to render MADR-compliant ADR stubs and a centralized design guide, automating architecture documentation.

Centralizing architecture documentation is best achieved by deriving design principles and patterns from a ProjectModel JSON, rendering a cohesive design guide and individual ADR stubs to ensure consistency and reduce manual drafting.

No, syncing generated design guidelines with an updated project model is not supported; the tool only provides init and update modes to manage the rendering of design guidelines and ADR stubs.

Yes, you need the docs-hero orchestrator tooling to render MADR-compliant design guidelines, as the CLI requires both a ProjectModel JSON and this orchestrator to manage outputs and ADR stubs.

You need to generate per-ADR stubs under a docs directory when establishing or updating architecture documentation for product teams, ensuring each architectural decision is recorded as a separate slug-named markdown file.