architect

Generates and updates ARCHITECTURE.md from a proven product specification.

1|Updated Jul 4, 2026
One-click install
npx skills add https://github.com/happysasha18/live-spec --skill architect-happysasha18
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architect
Source: https://github.com/happysasha18/live-spec/tree/main/skills/architect
Command: npx skills add https://github.com/happysasha18/live-spec --skill architect-happysasha18

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Specs drift from shipped code and structures grow without backing. This Skill derives or updates ARCHITECTURE.md from a proven PRODUCT_SPEC.md so every spec fact has exactly one owning node, every node pins to real file:line locations, and quality budgets carry measurable numbers. ## Core Features & Use Cases - Node structure derivation: Proposes named nodes and seams based on the project's kind (fullstack app, backend service, CLI, skill pack, content project), then lets the spec's facts decide the final map. - Reality pinning and budgets: Reconciles every node with shipped code via grep-verified file:line pins, and writes quality budgets with instrumentation homes and watchers. - Runtime, placement, and fitness views: Walks every promised flow through the nodes, states where each node runs and where secrets live, and applies a three-question fitness test to every new or carved node. - Use Case: Hand the Skill a proven spec for a fullstack app and receive an updated ARCHITECTURE.md with frontend, backend, and store nodes, named seams, a generated Reference table, and a coverage rule ensuring no orphan spec facts. ## Quick Start Use the architect skill to derive ARCHITECTURE.md from my proven PRODUCT_SPEC.md and pin every node to the shipped code.

Frequently Asked Questions about architect

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

FAQPage Schema
How do I generate an architecture document from a product spec?▼

Provide a proven PRODUCT_SPEC.md and the Skill derives ARCHITECTURE.md with named nodes, seams, quality budgets, and runtime and placement views. Each node must own at least one spec fact, and the project's kind proposes the starting structure.

How does the architecture stay in sync with shipped code?▼

Every node pins to file:line locations verified by actually running greps and reads, never from memory or summaries. When spec and code disagree, the spec is fixed to the shipped truth, always in that direction.

When should a new node be carved out of an existing one?▼

A new node must pass a three-question fitness test: it can be tested alone, a real second place needs it, and it can be worked in parallel without queuing on shared files. Two or more no answers means the carve is premature and folds back.

Can I use this Skill without a finished specification?▼

No. The Skill requires a proven spec because the derivation has nothing sound to build from otherwise. Requests to design structure with no spec behind them route to the spec-author skill first.

What checks verify the finished architecture document?▼

The product-prover skill runs an architecture lens checking that every spec fact has an owning node, no node lacks spec backing, seams name their crossings, budgets state instrumentation homes, and both views are complete. Findings land in docs/prover/.