agentleFS
oscal-compass-laboscal-compass-lab/compliance-trestle-skills/.cursor/skills/review-oscal-mappings/SKILL.md

review-oscal-mappings

Skill16 starsChanged 4 months agoApache-2.0View on GitHub

Review source-to-OSCAL mappings, triage needs_review rows, and update the review queue before treating generated OSCAL as ready for stakeholders.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    make sure the source text supports the OSCAL target

    line 22
  2. Distinctive:

    Use explicit statuses in the traceability map.

    line 37
  3. Distinctive:

    Do not silently rewrite uncertain source statements as implemented technical reality.

    line 54

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Review OSCAL Mappings

Human-in-the-loop review workflow for source traceability and mapping quality.

Read first

  • docs/OSCAL-REVIEW-WORKFLOW.md
  • adapters/generic-agent-package/prompts/review-oscal-mappings.md
  • plugins/document-transform/oscal-document-workbench/templates/review-queue.md
  • plugins/document-transform/oscal-document-workbench/templates/control-mapping-review.csv

Steps

  1. Load source-map.csv and any generated reports/review-queue.md.
  2. For each needs_review or unmapped row:
    • make sure the source text supports the OSCAL target
    • mark unsupported claims needs_review or reject
    • identify missing evidence
    • keep reviewer notes
  3. Make or update the review queue:
bash plugins/document-transform/oscal-document-workbench/scripts/build-review-queue.sh <workspace>/extracted/source-map.csv --output <workspace>/reports/review-queue.md
  1. Summarize counts of mapped, needs_review, and unmapped items.
  2. Block "ready for assessment" claims while unresolved review rows remain.

Reviewer decisions

Use explicit statuses in the traceability map.

Allowed source-map.csv statuses:

  • mapped
  • needs_review
  • unmapped
  • reject

Allowed reviewer decisions in the queue. Keep these separate from mapping status:

  • approve
  • remap
  • reject
  • needs_more_evidence
  • defer

Do not silently rewrite uncertain source statements as implemented technical reality.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.