skills.rest
chaimt
chaimtCOMMUNITY
Explore all skills by this author →
Website𝕏@chaimtGitHub

architect-specify

Transform PRDs into MADR-compliant Architecture Decision Records through guided exploration.

Updated Apr 21, 2026
Search Tags:#architecture#specification#adr#analysis#interactive#governance#prd
One-click install
npx skills add https://github.com/chaimt/GarminShabbatMode --skill architect-specify
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architect-specify
Source: https://github.com/chaimt/GarminShabbatMode/tree/main/.cursor/skills/architect-specify
Command: npx skills add https://github.com/chaimt/GarminShabbatMode --skill architect-specify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This capability helps product teams translate a PRD into structured Architecture Decision Records (ADRs) through guided discovery and formal documentation, ensuring traceability.

Core Features & Use Cases

  • Interactive PRD analysis that decomposes domains, captures requirements, and aligns with governance constraints.
  • Per-sub-system exploration that generates MADR-compliant ADRs and links decisions across subsystems.
  • Reference to constitution and project context to ensure consistent, auditable architecture decisions.

Quick Start

Provide your PRD context to start an interactive exploration that decomposes the system and generates ADRs.

Frequently Asked Questions about architect-specify

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

FAQPage Schema
How do I generate Architecture Decision Records from a PRD?▼

Generating ADRs from a PRD involves interactive domain decomposition and trade-off analysis, which captures requirements and outputs MADR-compliant Architecture Decision Records per sub-system.

What is the best way to document architecture decisions for greenfield projects?▼

Documenting architecture decisions for greenfield projects is best handled through guided PRD exploration that performs domain decomposition and outputs structured, auditable MADR-compliant ADRs.

Can I enforce governance constraints when creating architecture specifications?▼

Yes, you can enforce governance constraints when creating architecture specifications by loading constitution context during interactive PRD analysis to ensure consistent, auditable decisions across all sub-systems.

Does interactive PRD analysis support auto-decomposition for multi-domain systems?▼

Yes, interactive PRD analysis supports auto-decomposition for greenfield multi-domain systems, automatically breaking down PRDs into sub-systems to generate per-domain ADRs.

How do I link architecture decisions across multiple sub-systems?▼

Linking architecture decisions across multiple sub-systems requires coordinated context extraction during ADR generation, which connects related trade-off analyses and outputs linked MADR-compliant documentation.

When should I not use automated ADR generation for architecture analysis?▼

Automated ADR generation should not be used for architecture analysis when the input PRD lacks multiple domains or is not a greenfield project, as the auto-decomposition and governance loading features rely on greenfield multi-domain context.

Related Skills

Explore More Software Engineering Skills→
fcastrillofcastrillo

rai-project-create

Generate governance documents and a knowledge graph for new projects.

Community
Advanced
chaimtchaimt

speckit-adlc-architect-specify

Convert PRDs into MADR-compliant ADRs through guided interactive exploration.

Community
Advanced
JohannesKoningsJohannesKonings

to-prd

Synthesize conversation and codebase context into a product requirements document and publish it to the issue tracker.

Community
Intermediate
TwuanMinnTwuanMinn

architecture

Document architecture decisions using ADRs and structured trade-off analyses.

Community
Advanced