arch-lock

Extract architecture decisions from design documents and lock them in a state file.

2|1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/solitasroh/mcukit --skill arch-lock
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: arch-lock
Source: https://github.com/solitasroh/mcukit/tree/main/skills/arch-lock
Command: npx skills add https://github.com/solitasroh/mcukit --skill arch-lock

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Lock architecture decisions from Design documents to prevent scope creep during Do phase. Auto-generates Mermaid diagrams for MCU memory maps, MPU software stacks, WPF MVVM structures.

Core Features & Use Cases

  • Reads Design documents and extracts architecture decisions
  • Locks decisions in a state file and prevents edits outside unlocks
  • Generates Mermaid diagrams for domain architectures to aid reviews

Quick Start

Use /arch-lock lock <feature> to lock architecture decisions.

Frequently Asked Questions about arch-lock

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

FAQPage Schema
How do I enforce architecture decisions from design documents during development?

To enforce architecture decisions, you lock design constraints from design documents into a state file, preventing edits outside explicit unlocks. This stops scope creep during the Do phase execution.

Can I auto-generate Mermaid diagrams for MCU memory maps and WPF MVVM structures?

Yes, you can automatically generate Mermaid diagrams for MCU memory maps, MPU software stacks, and WPF MVVM structures. These diagrams aid domain architecture reviews and track ongoing design changes.

What is the best way to prevent scope creep when tracking architecture changes in embedded projects?

The best way to prevent scope creep is locking architecture decisions using the PDCA cycle. By anchoring design constraints and validating changes against locked boundaries, you maintain strict design governance across MCU and MPU projects.

Does arch-lock support validating code changes against locked architecture boundaries?

Yes, arch-lock supports validating changes by checking ongoing Do-phase execution against locked boundaries. It reads design documents, extracts decisions, stores locks, and ensures all modifications comply with the defined architecture.

How do I lock architecture decisions for a specific feature?

To lock architecture decisions for a specific feature, use the command '/arch-lock lock <feature>'. This extracts decisions from your design documents and stores them in a secure state file for governance.