superpowers-sage:architecture-discovery

To document architecture for a Sage WordPress theme, you map existing codebase components like ACF field groups, Livewire components, and Service Providers into a section-by-section spec for user approval.

Yes, you can generate an architecture spec from an unknown Acorn WordPress codebase by running parallel discovery probes that map content models, design tokens, and architectural constraints into a coherent decision package.

The best way to plan handoff for new features in a legacy WordPress repository is to map architectural boundaries and clarify feature scope into an unambiguous handoff payload for downstream plan generation.

No, architecture discovery for Sage and Acorn projects operates under strict no-implementation guardrails, focusing solely on producing an approved spec file and handoff payload rather than writing feature code.

You map ACF field groups and content models by running targeted discovery probes that analyze the existing WordPress codebase structure and synthesize the findings into an approved architecture spec.

You need an approved architecture spec for WordPress development when building new features in partially understood repositories to reduce guesswork, clarify requested feature scope, and establish safe architectural boundaries.