architect

Produce reviewable system architecture in `.claude/architecture.md` with stepwise checkpoints.

Updated Apr 30, 2026
One-click install
npx skills add https://github.com/jnlanahan/Product-Agents-and-Skills --skill architect-jnlanahan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architect
Source: https://github.com/jnlanahan/Product-Agents-and-Skills/tree/main/skills/3-Architect
Command: npx skills add https://github.com/jnlanahan/Product-Agents-and-Skills --skill architect-jnlanahan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents costly rework by making novel architecture decisions explicit and reviewable before implementation starts.

Core Features & Use Cases

  • Detects your current stack to ground architecture choices in reality and constraints (framework, database/ORM, auth, payments, monitoring, deploy target).
  • Designs the data model by defining entities, relationships, query patterns, and constraints like encryption and multi-tenancy.
  • Surfaces integrations and constraints by listing external/internal services, auth model, rate limits, failure modes, and compliance concerns.
  • Documents tradeoffs and rejected alternatives and optionally records load-bearing decisions as an ADR in .claude/decisions.md.
  • Produces a complete .claude/architecture.md synthesized from step outputs, with next-step prompts to plan and measure.

Quick Start

Run the architect skill for a greenfield SaaS feature design to generate a reviewable .claude/architecture.md that you can step through and approve.

Frequently Asked Questions about architect

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

FAQPage Schema
How do I document system architecture before starting implementation?

System architecture documentation is generated by detecting your stack, designing the data model, and surfacing integration constraints to produce a reviewable architecture.md file before coding begins.

What's the best way to record architecture tradeoffs and rejected alternatives?

Architecture tradeoffs and rejected alternatives are documented during the design process, with an option to record load-bearing decisions as Architecture Decision Records in a decisions.md file.

How do I design a data model for a greenfield SaaS product?

Data model design for greenfield products is accomplished by defining entities, relationships, query patterns, and constraints like encryption and multi-tenancy within the generated architecture document.

Can I use this to plan infrastructure changes for an existing stack?

Yes, significant infrastructure changes are supported by detecting your current stack frameworks, databases, and deploy targets to ground new architecture choices in your existing constraints.

Does this approach capture external integrations and rate limits?

External and internal integrations are explicitly captured by listing services, authentication models, rate limits, failure modes, and compliance concerns as part of the architecture review.

How do I step through and review an architecture plan step by step?

Reviewable architecture plans are produced stepwise with checkpoint pauses, allowing you to explicitly review and approve stack detection, data models, and integration constraints before proceeding.