skills.rest
Kohlex
KohlexOFFICIAL
Explore all skills by this author →
WebsiteGitHub

architecture-design

Generate an ARCHITECTURE.md design contract from WEDGE-AND-CAPABILITIES.md, capabilities.yaml, and PRD.

Updated Jun 4, 2026
Search Tags:#architecture#capabilities#architecture-design#design-contract#wedge#phase-0.5#lock_hash
One-click install
npx skills add https://github.com/Kohlex/autopilot-plugin --skill architecture-design-kohlex
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture-design
Source: https://github.com/Kohlex/autopilot-plugin/tree/main/skills/architecture-design
Command: npx skills add https://github.com/Kohlex/autopilot-plugin --skill architecture-design-kohlex

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Product-agnostic design artifact that converts an approved wedge, capabilities.yaml, PRD into a locked ARCHITECTURE.md design contract, anchoring downstream work and ensuring the lock_hash pins the architecture for all downstream capabilities.

Core Features & Use Cases

  • Generates a discipline-appropriate ARCHITECTURE.md with the required 10 sections and a pinned lock_hash.
  • Orchestrates input combination (WEDGE-AND-CAPABILITIES.md, capabilities.yaml, PRD.md, INTENT.md) to yield a repeatable, product-agnostic design artifact.
  • Defines module boundaries, data-model skeleton, integration seams, and cross-cutting concerns to guide Phase-0.5 gate workflows and escalation paths.

Quick Start

Run /architecture-design <product> to draft ARCHITECTURE.md from WEDGE-AND-CAPABILITIES.md, capabilities.yaml, PRD.md, and INTENT.md.

Frequently Asked Questions about architecture-design

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

FAQPage Schema
How do I generate an architecture design contract from a PRD and capabilities graph?▼

To generate an architecture design contract, you combine WEDGE-AND-CAPABILITIES.md, capabilities.yaml, PRD.md, and INTENT.md to produce a locked ARCHITECTURE.md defining module boundaries, data-model skeleton, and integration seams.

What is a lock_hash in an architecture design contract?▼

A lock_hash is a pinned reference stored in capabilities.yaml that locks the architecture for all downstream capabilities, ensuring the generated ARCHITECTURE.md design contract anchors and constrains downstream work.

How do I define module boundaries and integration seams during Phase-0.5?▼

You define module boundaries and integration seams by consuming the approved wedge and capabilities graph, which yields a product-agnostic ARCHITECTURE.md artifact guiding Phase-0.5 gate workflows and escalation paths.

What inputs are required to draft an ARCHITECTURE.md design contract?▼

Required inputs to draft an ARCHITECTURE.md design contract include WEDGE-AND-CAPABILITIES.md, capabilities.yaml, PRD.md, and INTENT.md, with optional capability-maps and prior research to enrich the output.

Can I use this architecture design flow for any product or tech stack?▼

Yes, you can apply this flow to any product by consuming the wedge and capabilities graph to define tech-stack decisions, data-model skeleton, and integration seams in a product-agnostic design artifact.

What sections are included in a generated architecture design contract?▼

The generated architecture design contract includes a discipline-appropriate ARCHITECTURE.md with ten required sections and a pinned lock_hash, covering cross-cutting concerns and integration seams for downstream capabilities.

Related Skills

Explore More Software Engineering Skills→
KohlexKohlex

stakeholder-summary-generator

Generate EXECUTIVE-SUMMARY.md and WHY-WHAT-HOW.md from PRD, wedge, and architecture inputs.

Official
Intermediate
KohlexKohlex

architecture-stress-test

Run three adversarial lenses on ARCHITECTURE.md and capabilities.yaml to produce a STRESS-TEST-REPORT.md.

Official
Advanced
KohlexKohlex

wedge-synthesis

Synthesize capability-maps and hypotheses into wedge and dependency artifacts.

Official
Advanced
imkdwimkdw
1

Global Tech Stack

Explain the project's tech stack and guide architecture decisions.

Community
Intermediate