arch

Generate a living architecture specification with subsystem contracts, constraints, and build order.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/madebymlai/feldspar --skill arch-madebymlai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: arch
Source: https://github.com/madebymlai/feldspar/tree/main/.claude/skills/arch
Command: npx skills add https://github.com/madebymlai/feldspar --skill arch-madebymlai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Projects often lack a coherent, living architecture that defines subsystem boundaries, contracts, constraints, and build order, leading to misaligned designs and costly rework. This skill generates a structured, up‑to‑date global architecture specification that tracks project state and guides downstream development.

Core Features & Use Cases

  • Scope Clarification: Interactive dialog to extract user goals, constraints, and dependencies.
  • First‑Principles Analysis: Deconstructs requirements, challenges assumptions, and rebuilds subsystems from fundamentals.
  • Context Review: Searches existing docs, patterns, and style guides to align with project history.
  • Technical Validation: Weights local docs, library references, and web research to verify architectural choices.
  • Iterative Discussion: Conversational loops to refine decomposition before finalizing.
  • Adversarial Review & Manifest: Runs automated critique, generates a formal spec and manifest for build tracking.

Quick Start

Generate an architecture spec for the project brief at /path/to/brief.md using the arch skill.

Frequently Asked Questions about arch

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

FAQPage Schema
How do I create a living architecture specification for a greenfield project?

To create a living architecture specification, interactive dialog extracts project goals and constraints, then first-principles analysis decomposes the project into subsystems with formal contracts, constraints, and build order.

What is the best way to define subsystem boundaries and validate technical approaches?

The best way to define subsystem boundaries is through iterative discussion and adversarial review, which challenge assumptions and validate technical approaches against local docs, library references, and web research.

Can I generate an architecture manifest from an existing project brief?

Yes, you can generate an architecture manifest from an existing project brief by applying context review to search existing documentation and patterns, then producing a formal spec and manifest for build tracking.

Does automated adversarial review help validate architecture contracts?

Automated adversarial review validates architecture contracts by running automated critiques that challenge assumptions, ensuring comprehensive and consistent decomposition before finalizing the formal specification.

When do I need a formal architecture specification with build order tracking?

You need a formal architecture specification with build order tracking when projects lack coherent subsystem boundaries and contracts, leading to misaligned designs and costly rework during downstream development.