superpowers-sage:architecting

Name: superpowers-sage:architecting
Availability: InStock
Author: Hekivo

Define Sage/Acorn feature architecture with design-system validation and dependency-aware plans.

13|Updated Mar 19, 2026

Search Tags:#planning #architecture #design system #ADR #dependency mapping #Sage #Acorn

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you define a clear, validated architecture for a Sage/Acorn feature before writing any implementation, reducing rework and misalignment between UI, data flow, and component boundaries.

Core Features & Use Cases

Design system foundation gate: Verifies that design tokens and a kitchensink route/view exist before proceeding for multi-block/UI-heavy work.
Architecture discovery orchestration: Runs the discovery skill and requires explicit user approval of the produced architecture spec.
Plan generation and transition: Generates a build plan with dependencies and execution ordering, then hands off to execution-oriented skills when ready.

Use case: You’re adding a new multi-block Sage/Acorn feature and need architecture decision records, component boundaries, and dependency-mapped execution before coding.

Quick Start

Ask your agent to run superpowers-sage:architecting with the feature scope you want to add and approve the resulting architecture spec.

Frequently Asked Questions about superpowers-sage:architecting

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

FAQPage Schema

How do I define architecture for a new Sage feature before writing code?▼

To define architecture for a Sage feature, you coordinate design-system validation, architecture discovery, and dependency-aware plan generation. This process establishes component boundaries and data-flow mapping while enforcing a hard no-implementation gate until you approve the architecture spec.

What is an ADR-oriented pre-implementation design workflow?▼

An ADR-oriented pre-implementation design workflow is a process that maps architecture decisions and dependency execution ordering before any coding begins. It generates a validated build plan and requires explicit user approval of the architecture spec to prevent misalignment and rework.

Do I need design tokens and a kitchensink route before planning UI-heavy Sage features?▼

Yes, design tokens and a kitchensink route must exist before planning UI-heavy Sage features. The architecture workflow validates these design-system foundations exist as a prerequisite gate before proceeding with multi-block feature architecture discovery.

How does dependency mapping work when generating a Sage build plan?▼

Dependency mapping in a Sage build plan works by analyzing component boundaries and data flows to determine execution ordering. The generated plan maps these dependencies and then hands off to execution-oriented skills for implementation after you approve the spec.

Can I write implementation code while the Sage architecture discovery is running?▼

No, you cannot write implementation code during Sage architecture discovery because the workflow enforces a hard no-implementation gate. It requires explicit user approval of the produced architecture spec before transitioning to any execution-oriented build phase.

When should I use an architecture planning skill instead of direct coding for Acorn features?▼

You should use an architecture planning skill for Acorn features when adding multi-block functionality that requires clear component boundaries and data-flow mapping. It prevents rework by validating design-system foundations and dependency ordering before you start coding.