architect

Manage Markdown dx file lifecycle by enforcing invariants and contracts.

1|Updated May 12, 2026

Search Tags:#architecture #specification #governance #dx #contracts #invariants

Ready to run

npx skills add https://github.com/dewitt/dx --skill architect-dewitt

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architect
Source: https://github.com/dewitt/dx/tree/main/skills/architect
Command: npx skills add https://github.com/dewitt/dx --skill architect-dewitt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents architectural drift by ensuring that software declarations remain the single source of truth, keeping intent, invariants, and contracts synchronized with implementation.

Core Features & Use Cases

Constraint Management: Enforces a minimum viable constraint set to prevent over-engineering.
Semantic Auditing: Validates changes to declarations using linting and diffing to ensure structural integrity.
Role-Based Workflow: Facilitates the handoff between architects, implementers, and judges by formalizing how assumptions are promoted to invariants.

Quick Start

Ask the architect to review the current declaration and promote any verified assumptions to invariants.

Frequently Asked Questions about architect

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

FAQPage Schema

How do I prevent architectural drift in software specifications?▼

To prevent architectural drift, you can use Markdown-based dx files managed through invariant and contract enforcement. This approach keeps system intent, invariants, and contracts synchronized with implementation to maintain a stable, minimal constraint set.

What is the best way to audit software declarations for structural integrity?▼

Auditing software declarations is best handled through semantic linting and diffing. This validates architectural changes against declarative specifications to ensure structural integrity and prevent over-engineering across multiple implementations.

How do I manage invariants and contracts in declarative software specifications?▼

Managing invariants and contracts requires enforcing a minimum viable constraint set within Markdown-based dx files. This maintains a stable architecture by validating changes through semantic diffing and keeping declarations the single source of truth.

How does a role-based workflow formalize assumptions into architectural invariants?▼

A role-based workflow formalizes architectural invariants by facilitating the handoff between architects, implementers, and judges. You can review current declarations to promote any verified assumptions to permanent invariants.

When do I need to use semantic diffing for software architecture changes?▼

Semantic diffing is needed when validating architectural changes to declarative software specifications. It ensures structural integrity is maintained and that system intent remains observable and auditable across multiple implementations.