create-control-manifest

Name: create-control-manifest
Availability: InStock
Author: carlosq96

Generate a flat control manifest from Accepted ADRs and technical preferences.

Updated Apr 9, 2026

Search Tags:#automation #architecture #documentation #adr #engineering #manifest #guidelines

Ready to run

npx skills add https://github.com/CarlosQ96/robot-crawler --skill create-control-manifest

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-control-manifest
Source: https://github.com/CarlosQ96/robot-crawler/tree/main/.agents/skills/create-control-manifest
Command: npx skills add https://github.com/CarlosQ96/robot-crawler --skill create-control-manifest

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It provides a flat, actionable rules sheet for programmers, consolidating Accepted ADRs, technical preferences, and engine reference docs into a single manifest that helps teams implement architecture decisions consistently.

Core Features & Use Cases

Consolidates ADRs, technical preferences, and engine references into a unified control manifest.
Classifies rules by architectural layer (Foundation, Core, Feature, Presentation) and captures global guidelines.
Generates and updates docs/architecture/control-manifest.md after architecture reviews and ADR approvals, enabling consistent development.

Quick Start

Run the manifest generator after architecture review passes to produce docs/architecture/control-manifest.md.

Frequently Asked Questions about create-control-manifest

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

FAQPage Schema

How do I generate an architecture control manifest from ADRs?▼

To generate an architecture control manifest from ADRs, the Skill extracts rules from Accepted ADRs, technical preferences, and engine reference docs, then outputs a flat, actionable rules sheet to docs/architecture/control-manifest.md.

What is a control manifest and how does it consolidate ADRs?▼

A control manifest is a flat, actionable rules sheet that consolidates Accepted ADRs, technical preferences, and engine reference docs into a single document for programmers to implement architecture decisions consistently.

How are architectural rules classified by layer in the generated manifest?▼

Architectural rules are classified by layer into Foundation, Core, Feature, and Presentation layers, while global conventions are captured separately to ensure structured organization in the control manifest.

When should I run the manifest generator for my engineering team?▼

You should run the manifest generator after an architecture review passes or when ADRs change, ensuring the control manifest is updated to reflect the latest accepted architectural decisions for consistent development.

Does the control manifest generator work without external dependencies?▼

Yes, the control manifest generator works without external dependencies, loading Accepted ADRs and engine reference docs directly to output the manifest to docs/architecture/control-manifest.md.

What is the best way to maintain a control manifest when ADRs change?▼

The best way to maintain a control manifest when ADRs change is to run the generator to reload Accepted ADRs, re-extract rules by layer, and update docs/architecture/control-manifest.md automatically.