master-control-expert

To turn unstructured requests into governed workflows, you classify the request into A–H categories, run a mandatory universal intake checklist, and generate an actionable control plan with artifacts and decision logs.

A universal intake checklist for workflow governance captures context, constraints, and inputs before execution, ensuring requests are classified and mapped to an actionable control plan with concrete deliverables.

You generate decision logs and artifacts by applying prompt-skeleton execution from the prompt catalog to the classified task, producing files, data blocks, and step-by-step instructions for immediate handoff.

Yes, you can create new workflow categories through self-evolution triggers that initiate new-category or prompt-improvement workflows based on ongoing usage and feedback.

Deliverables from a governance-backed control plan include concrete files, data blocks, step-by-step instructions, runbooks, decision logs, and success criteria ready for immediate handoff.

No specific dependencies are required; the framework applies universal intake and category classification across A–H categories to produce governance-backed workflows and artifacts independently.