fedramp-ssp-expert

Convert FedRAMP Rev 5 Word-template SSPs into OSCAL 1.2.0 JSON.

Updated Apr 25, 2026
One-click install
npx skills add https://github.com/abnejsolutions-alt/GRC --skill fedramp-ssp-expert
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fedramp-ssp-expert
Source: https://github.com/abnejsolutions-alt/GRC/tree/main/plugins/fedramp-ssp/skills/fedramp-ssp-expert
Command: npx skills add https://github.com/abnejsolutions-alt/GRC --skill fedramp-ssp-expert

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams convert FedRAMP Rev 5 Word-template SSPs into a machine-readable OSCAL 1.2.0 representation, enabling automated validation and external auditing.

Core Features & Use Cases

  • DOCX→OSCAL pipeline for main SSP plus Appendix A to JSON
  • Output contents include metadata, system-characteristics, system-implementation, control-implementation, and back-matter
  • Use Case: when an organization needs to submit an OSCAL SSP to a 3PAO or AO or migrate FedRAMP data into an automation pipeline.

Quick Start

Supply a filled FedRAMP SSP DOCX and run the OSCAL translation workflow to generate the 1.2.0 SSP in OSCAL JSON.

Frequently Asked Questions about fedramp-ssp-expert

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

FAQPage Schema
How do I convert a FedRAMP SSP Word document into OSCAL format?

To convert a FedRAMP SSP Word document into OSCAL format, supply the filled Rev 5 DOCX template to the translation workflow. The process generates a structured 1.2.0 OSCAL JSON SSP including metadata, system-characteristics, and control-implementation for automated validation.

What is the OSCAL output structure for a converted FedRAMP SSP?

The OSCAL output structure for a converted FedRAMP SSP includes metadata, system-characteristics, system-implementation, control-implementation, and back-matter. It utilizes FedRAMP-namespaced fields to ensure compatibility with 3PAO and AO reviews.

Can I use the generated OSCAL SSP for eMASS imports and compliance pipelines?

Yes, you can use the generated OSCAL SSP for eMASS imports and compliance pipelines. The machine-readable 1.2.0 OSCAL JSON output is specifically designed to enable automated validation, external auditing, and integration into compliance pipelines.

Does the DOCX to OSCAL conversion include FedRAMP Appendix A?

Yes, the DOCX to OSCAL conversion includes FedRAMP Appendix A. The pipeline processes the main SSP along with Appendix A to produce a complete OSCAL JSON representation suitable for 3PAO or AO submission.

What FedRAMP template version is supported for OSCAL translation?

The OSCAL translation supports FedRAMP Rev 5 Word-template SSPs. It converts these specific DOCX templates into the OSCAL 1.2.0 standard using FedRAMP-namespaced fields for accurate system representation.