From fedramp-ssp
Install the frdocx-to-froscal-ssp Python pipeline and verify its dependencies. Idempotent.
npx claudepluginhub rifh2000/claude-grc-engineering. --plugin fedramp-ssp# /fedramp-ssp:setup Prepares the SSP DOCX→OSCAL pipeline. Clones `ethanolivertroy/frdocx-to-froscal-ssp`, installs its Python requirements into a dedicated virtualenv, and records the install path. ## How to run ## What it does 1. Detect Python ≥ 3.10. `--python=/opt/homebrew/bin/python3.12` overrides. 2. Clone/update `ethanolivertroy/frdocx-to-froscal-ssp` into `~/.local/share/claude-grc/tools/frdocx-to-froscal-ssp`. 3. Create a virtualenv at `<tool-dir>/.venv` and `pip install -r requirements.txt` (primarily `python-docx`). 4. Verify that the entry-point script runs (`python cli.py...
/setupInitializes or resumes project setup via interactive Q&A, creating conductor/ artifacts for product definition, guidelines, tech stack, workflow, and style guides.
/setupDetects ghost or inconsistent claude-hud plugin installations (orphaned cache, stale registry, temp files) and offers cleanup on user confirmation for macOS/Linux/Windows.
/setupChecks local Codex CLI readiness, prompts to install if unavailable via npm, and optionally toggles stop-time review gate.
/setupGuides enterprise admins through Claude Office add-in setup for Vertex AI, Bedrock, or custom gateway; provisions credentials and generates deployable manifest.xml.
/setupRuns interactive setup wizard: detects AI providers (Codex, Gemini, Ollama, etc.), installs missing ones via Bash, configures auth, and sets up RTK token optimization.
Prepares the SSP DOCX→OSCAL pipeline. Clones ethanolivertroy/frdocx-to-froscal-ssp, installs its Python requirements into a dedicated virtualenv, and records the install path.
bash plugins/fedramp-ssp/scripts/setup.sh [--python=<python3-executable>]
Detect Python ≥ 3.10. --python=/opt/homebrew/bin/python3.12 overrides.
Clone/update ethanolivertroy/frdocx-to-froscal-ssp into ~/.local/share/claude-grc/tools/frdocx-to-froscal-ssp.
Create a virtualenv at <tool-dir>/.venv and pip install -r requirements.txt (primarily python-docx).
Verify that the entry-point script runs (python cli.py --help or equivalent).
Warn (not fail) if Java 17 isn't available — it's only needed for optional oscal-cli validation inside the pipeline; the /oscal:validate command from this toolkit can fill that role.
Write config:
version: 1
source: fedramp-ssp
source_version: "0.1.0"
python: "/opt/homebrew/bin/python3.12"
venv: "~/.local/share/claude-grc/tools/frdocx-to-froscal-ssp/.venv"
tool_dir: "~/.local/share/claude-grc/tools/frdocx-to-froscal-ssp"
oscal_version: "1.2.0"
fedramp-ssp:setup ✓
python: /opt/homebrew/bin/python3.12 (3.12.5)
tool dir: ~/.local/share/claude-grc/tools/frdocx-to-froscal-ssp
venv: ready (python-docx installed)
java: OpenJDK 17.0.11 (optional, available)
config: ~/.config/claude-grc/connectors/fedramp-ssp.yaml
Next:
/fedramp-ssp:convert --ssp-docx=<path> --appendix-a-docx=<path>
--python=<path>./oscal:validate downstream instead of the tool's bundled validation step.