Skill

superpowers-sage:architecture-discovery

Maps architecture of Sage/Acorn WordPress codebases: discovers post types, routes, ACF field groups, Livewire components, Service Providers; identifies gaps, generates ADRs, diagrams, specs.

Php

Laravel

backend

documentation

npx claudepluginhub codigodoleo/superpowers-sage --plugin superpowers-sage

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Design-first architecture workflow for WordPress + Sage + Acorn + Lando projects.

Supporting Assets

references/discovery-procedures.mdreferences/output-contract.md

SKILL.md

Similar Skills

superpowers-sage:architecting

Orchestrates architecture discovery and plan generation for Sage/Acorn features, including ADRs, component boundaries, data flow, dependency mapping, and design system validation.

superpowers-sage

analyze-architecture

Scans codebase and generates high-level architecture graph as interlinked markdown files in docs/professor/architecture/. Use for new project analysis or significant changes.

claude-professor

architect

Use when the user needs to plan and architect a new feature before implementation begins. This includes analyzing requirements, asking clarifying questions, and creating a detailed implementation plan aligned with the project's architecture. Invoke BEFORE any coding work starts.

1 file

craft-skills

Stats

Stars10

Forks0

Last CommitApr 20, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Architecture Discovery

Design-first architecture workflow for WordPress + Sage + Acorn + Lando projects.

Announce at start: "I'm using architecture-discovery to produce an approved architecture spec before any implementation plan."

Input

$ARGUMENTS

HARD GATES

Never write implementation code in this skill.
Never invoke superpowers-sage:building before architecture approval and plan generation.
Never skip section-by-section approval.

Procedure (summary)

Full step-by-step procedures for each phase are in references/discovery-procedures.md.

Branch & scope — ensure feature branch exists, normalize scope in one sentence.
Explore context — read config/poet.php, existing blocks, providers, active plans.
Clarifying questions — gather requirements one at a time (UX, editor, integrations, constraints).
Identify components — list with responsibility, inputs/outputs, dependencies, risks.
Parallel probes — dispatch content-modeler, design-extractor (PANORAMIC), sage-reviewer in parallel; synthesize.
Propose approaches — 2-3 options with trade-offs; ask user to choose. Apply AD-2 preset if porting legacy schemas.
Decision graph — classify tasks as parallel/sequential/gated.
Section: Overview — present + ask approval.
Section: Components & data flow — present + ask approval.
Section: Quality strategy — present + ask approval.
Write spec — docs/superpowers/specs/YYYY-MM-DD-<topic>-architecture.md. Commit.
Spec review loop — dispatch sage-reviewer up to 3 times; escalate on persistent failure.
User approval gate — revise until approved.
Handoff — prepare handoff payload; invoke superpowers-sage:plan-generator.

For detailed procedure steps and the AD-2 preset block, read skills/architecture-discovery/references/discovery-procedures.md.

Output Contract

Full output artifact specifications are in references/output-contract.md.

Required outputs:

Approved architecture spec at docs/superpowers/specs/YYYY-MM-DD-<topic>-architecture.md
Review feedback resolved or explicitly waived
Complete handoff payload for superpowers-sage:plan-generator

For spec template and handoff payload format, read skills/architecture-discovery/references/output-contract.md.

Verification

Before completion, confirm all items:

Spec file exists at docs/superpowers/specs/YYYY-MM-DD-<topic>-architecture.md
Spec has user approval recorded in conversation
At least one reviewer loop executed (or explicit user waiver)
Handoff payload is complete and unambiguous

Failure modes

No design reference available: proceed text-first, mark visual assumptions explicitly.
Scope too broad: decompose into sub-projects and complete first sub-scope only.
Repeated reviewer failures: escalate after 3 attempts.
Missing content model signal: re-run superpowers-sage:content-modeler before finalizing spec.