superpowers-sage:architecture-discovery

Name: superpowers-sage:architecture-discovery
Availability: InStock
Author: Hekivo

Map Sage/Acorn codebases into approved architecture specs with handoff payloads.

13|Updated Mar 19, 2026

Search Tags:#decision records #wordpress #architecture discovery #sage #acorn #acf field groups #handoff planning

Ready to run

npx skills add https://github.com/hekivo/superpowers-sage --skill superpowers-sage-architecture-discovery-hekivo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: superpowers-sage:architecture-discovery
Source: https://github.com/hekivo/superpowers-sage/tree/main/skills/architecture-discovery
Command: npx skills add https://github.com/hekivo/superpowers-sage --skill superpowers-sage-architecture-discovery-hekivo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill reduces costly guesswork by turning an existing Sage/Acorn codebase and an unclear feature scope into an approved, section-by-section architecture spec you can safely build from.

Core Features & Use Cases

Codebase-to-architecture mapping: Maps components, routes, post types, ACF field groups, Livewire components, Service Providers, and architectural boundaries.
Parallel discovery probes: Runs targeted probes (content modeling, design extraction, and Sage review) and synthesizes results into a coherent decision package.
Approval-gated output: Forces hard gates and requires user approval for each major section before generating downstream plans.
Architecture spec + handoff: Writes the approved spec to docs/superpowers/specs and prepares a handoff payload for plan generation.

Quick Start

Run architecture-discovery with your feature or scope description, then approve each section until the architecture spec is written and handed off for planning.

Frequently Asked Questions about superpowers-sage:architecture-discovery

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I document architecture for a Sage WordPress theme before adding new features?▼

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.

Can I generate an architecture spec from an unknown Acorn WordPress codebase?▼

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.

What is the best way to plan handoff for new features in a legacy WordPress repository?▼

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.

Does architecture discovery write implementation code for Sage and Acorn projects?▼

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.

How do I map ACF field groups and content models in an existing WordPress codebase?▼

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.

When do I need an approved architecture spec for WordPress development?▼

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.