create-control-manifest

Generate a Control Manifest with per-layer rules and global constraints from ADRs.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/emcconnell/nova-scout --skill create-control-manifest-emcconnell
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-control-manifest
Source: https://github.com/emcconnell/nova-scout/tree/main/.claude/skills/create-control-manifest
Command: npx skills add https://github.com/emcconnell/nova-scout --skill create-control-manifest-emcconnell

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Control Manifest consolidates architectural rules from Accepted ADRs, technical preferences, and engine references into a single, actionable sheet that tells programmers what to do and what not to do.

Core Features & Use Cases

  • Outputs a per-layer rule set (Foundation, Core, Feature, Presentation) plus global constraints for governance.
  • Regenerates automatically when ADRs or engine references are updated to keep compliance current.
  • Provides traceability from ADRs to implementation guidance to speed onboarding and audits.

Quick Start

Run the manifest generator after the 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
What is a control manifest in software architecture governance?

A control manifest is a flat, actionable document that codifies rules from ADRs, technical preferences, and engine docs. It provides developers with per-layer and global constraints to ensure engineering compliance and proper governance.

How do I consolidate ADRs and technical preferences into actionable developer guidelines?

You can consolidate ADRs and technical preferences by generating a control manifest, which outputs a single markdown file organizing architectural rules by layer (Foundation, Core, Feature, Presentation) and global governance constraints.

When do I need to generate a control manifest for my project?

You need to generate a control manifest after your architecture review passes and whenever ADRs or engine references are updated. This keeps developer implementation guidance and compliance traceability current.

Can I trace implementation guidance back to specific architecture decision records?

Yes, the control manifest provides traceability from accepted ADRs directly to implementation guidance. This consolidation speeds up developer onboarding and simplifies governance audits by mapping rules to decisions.

What is the best way to maintain engineering compliance when ADRs change?

The best way to maintain compliance is to regenerate the control manifest automatically when ADRs or engine references are updated. This ensures the actionable guidance provided to developers reflects the latest architectural decisions.

Does generating a control manifest require specific engine documentation inputs?

Yes, generating the manifest reads accepted ADRs, technical preferences, and engine references as inputs. These sources are consolidated into per-layer rules and global guidelines for the docs/architecture/control-manifest.md output.