From superpowers-sage
Orchestrates architecture discovery and plan generation for Sage/Acorn features, including ADRs, component boundaries, data flow, dependency mapping, and design system validation.
npx claudepluginhub codigodoleo/superpowers-sage --plugin superpowers-sageThis skill uses the workspace's default tool permissions.
This skill remains available to avoid breaking existing workflows. It now orchestrates the new split flow:
Maps architecture of Sage/Acorn WordPress codebases: discovers post types, routes, ACF field groups, Livewire components, Service Providers; identifies gaps, generates ADRs, diagrams, specs.
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.
Explores project context, asks clarifying questions, proposes 2-3 design approaches with trade-offs, presents designs section-by-section for approval, and writes spec docs before implementation.
Share bugs, ideas, or general feedback.
This skill remains available to avoid breaking existing workflows. It now orchestrates the new split flow:
superpowers-sage:architecture-discoverysuperpowers-sage:plan-generatorAnnounce at start: "I'm using architecting compatibility mode and will run architecture-discovery then plan-generator."
$ARGUMENTS
Do not implement code in this skill. If implementation is requested, complete the split planning flow first.
Before starting architecture discovery, check whether the visual foundation exists:
resources/css/design-tokens.css exist and contain real tokens (not a placeholder)?resources/views/kitchensink.blade.php or /kitchensink is accessible)?If both are present: proceed to Step 1 normally.
If either is missing or unvalidated:
⚠ Design system foundation not found.
Architecture for multi-block features should follow a validated design system.
Tokens, UI atoms, and layout components must exist before defining block schemas.
Recommendation: run /sage-design-system first.
→ It will create design-tokens.css, ui/ + layout/ Blade components, and validate with a kitchensink page.
→ Return to /architecting after the kitchensink screenshot is confirmed.
Proceed anyway? (only if this feature has no visual blocks / is purely backend)
Wait for explicit user confirmation before skipping the design system gate.
superpowers-sage:architecture-discovery with the same arguments.superpowers-sage:plan-generator with the approved spec path.After plan generation, offer:
subagent-driven-development for parallel task execution in this sessionsuperpowers-sage:building for direct implementation from plan filesdocs/superpowers/specs/YYYY-MM-DD-<topic>-architecture.mddocs/plans/YYYY-MM-DD-<topic>/plan.mdsuperpowers-sage:plan-generator.superpowers-sage:architecture-discovery review loop.superpowers-sage:plan-generator.