architect

Explore parallel module interface designs and capture a recommended architecture.

71|17|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/AgentiveStack/skills --skill architect-agentivestack
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architect
Source: https://github.com/AgentiveStack/skills/tree/main/architect
Command: npx skills add https://github.com/AgentiveStack/skills --skill architect-agentivestack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Surface architectural friction in the codebase and design better module interfaces. Uses parallel sub-agents to explore radically different interface designs. Based on "deep modules" philosophy — small interfaces hiding significant complexity. Use when code feels tangled, hard to test, or hard to navigate.

Core Features & Use Cases

  • Surface architectural friction across modules and contracts.
  • Propose multiple deep-module interface designs via parallel exploration.
  • Capture recommended interface with documentation and trade-offs.

Quick Start

Start a parallel exploration to surface architectural friction and propose a deep-module interface with a recommended design.

Frequently Asked Questions about architect

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

FAQPage Schema
How do I surface architectural friction in a tangled codebase?

To surface architectural friction, you analyze modules that are hard to test or navigate. This process discovers codebase context and uses parallel sub-agents to evaluate radically different interface designs, identifying where contracts are tangled.

What is the deep modules philosophy for software architecture?

The deep modules philosophy advocates for small interfaces hiding significant complexity. It improves code quality by ensuring module contracts are simple externally while managing substantial implementation depth internally, reducing architectural friction.

How do I design better module interfaces for hard-to-test code?

Design better module interfaces by running multiple exploratory designs in parallel. The system spawns sub-agents to evaluate radically different approaches, captures the recommended design, and documents trade-offs and rationale for the refactoring.

Can I explore multiple interface designs at the same time?

Yes, you can explore multiple interface designs simultaneously through parallel exploration. The system spawns parallel sub-agents to evaluate radically different interfaces, allowing you to compare architectural options and capture the recommended design.

When should I use parallel exploration for refactoring?

Use parallel exploration for refactoring when code feels tangled, hard to test, or hard to navigate. It is designed for codebases where software architecture needs radical rethinking to surface friction and propose deep modules.