converting-frameworks-to-controls

Maps compliance framework requirements to Fianu controls and generates a human-reviewed mapping report.

1|Updated Jun 11, 2026
One-click install
npx skills add https://github.com/fianulabs/fianu-skills --skill converting-frameworks-to-controls-fianulabs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: converting-frameworks-to-controls
Source: https://github.com/fianulabs/fianu-skills/tree/main/skills/converting-frameworks-to-controls
Command: npx skills add https://github.com/fianulabs/fianu-skills --skill converting-frameworks-to-controls-fianulabs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Ingesting a compliance framework (like SOC 2 or ISO 27001) into a governance platform requires manually reading every requirement, deciding whether an existing control covers it, and designing new controls where gaps exist. This Skill automates that analysis while keeping a human in the loop before anything is created. ## Core Features & Use Cases - Framework Parsing and Classification: Normalizes framework documents into requirements classified as automated, manual, hybrid, or informational. - Control Matching and Design: Matches requirements against existing published controls with similarity scores, and designs new controls including evidence plugin selection, Rego rules, policy templates, scope, and hierarchy placement. - Human-Gated Mapping Report: Produces a structured report with confidence scores and halts until a human approves, then creates draft controls and policies via the Fianu API. - Use Case: Given a SOC 2 document, generate a report showing which requirements reuse existing controls, which need new controls with suggested plugins and Rego rules, and which require manual attestation. ## Quick Start Analyze the attached SOC 2 framework document and produce a mapping report of requirements to Fianu controls for my review.

Frequently Asked Questions about converting-frameworks-to-controls

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

FAQPage Schema
How do I convert a compliance framework into controls?▼

Provide the framework document and the workflow parses it into normalized requirements, classifies each as automated, manual, hybrid, or informational, then matches them against existing controls or designs new ones. A mapping report is generated for human review before any drafts are created.

How are new controls designed for unmatched requirements?▼

For unmatched automated or hybrid requirements with classification confidence of 0.80 or higher, the workflow selects an evidence plugin, discovers its schema, writes an OPA v1 Rego rule, designs a matching policy template, picks a scope, and places the control in the entity hierarchy.

Does the workflow create controls automatically without approval?▼

No. The agent halts after generating the mapping report and does not create any drafts until a human explicitly approves the report. Approved rows then create draft controls and policies, which themselves require ticket approval before publishing.

What happens when a requirement has no matching evidence plugin?▼

If a requirement is classified as automated but no plugin in the catalog can supply the evidence, the workflow recommends an API-sourced control using a custom integration and flags the gap in the mapping report.

How are low-confidence or vague requirements handled?▼

Requirements with classification confidence below 0.80, possible matches scoring 0.50 to 0.79, or vague wording are placed in the Requires Human Review section of the report rather than being silently committed.