メニュー
Knowledge about Compliance Trestle workspace structure, initialization, and directory conventions. Use when users ask about trestle workspaces, directory layout, .trestle config, model directories, or how to set up and organize an OSCAL compliance workspace.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Knowledge about writing control implementation responses, rules, parameters, component-level responses, inheritance, and leveraged SSPs in Compliance Trestle. Use when users ask about writing control responses, implementation status, rules, parameters, component definitions, SSP implementation details, or compliance documentation content.
Knowledge about OSCAL model types, their relationships, and how they are managed in Compliance Trestle. Use when users ask about OSCAL documents, model types, catalogs, profiles, SSPs, component definitions, or how different compliance models relate to each other.
Knowledge about Compliance Trestle validation, common errors, and troubleshooting. Use when users ask about validation errors, trestle validate failures, OSCAL schema validation, fixing compliance document issues, or troubleshooting trestle problems.
Convert, validate, and maintain OSCAL documents from legacy SSP/PDF/DOCX/Markdown source material.
Import a legacy SSP, PDF, DOCX, or Markdown package into a traceable OSCAL Document Workbench workspace using extraction, source mapping, Trestle bootstrap, and validation.
Review source-to-OSCAL mappings, triage needs_review rows, and update the review queue before treating generated OSCAL as ready for stakeholders.
| name | trestle-workspace |
| description | Knowledge about Compliance Trestle workspace structure, initialization, and directory conventions. Use when users ask about trestle workspaces, directory layout, .trestle config, model directories, or how to set up and organize an OSCAL compliance workspace. |
| allowed-tools | Bash, Read, Glob, Grep, Write, Edit |
UserWarning. It is expected on unsupported versions; 3.11/3.12 avoids it entirely.pip install compliance-trestleA trestle workspace is an opinionated directory structure (similar to git) that manages OSCAL compliance documents.
.
├── .trestle/ # Config dir (config.ini, cache, templates)
├── dist/ # Assembled output files
│ ├── catalogs/
│ ├── profiles/
│ ├── component-definitions/
│ ├── system-security-plans/
│ ├── assessment-plans/
│ ├── assessment-results/
│ └── plan-of-action-and-milestones/
├── catalogs/ # Catalog source models
├── profiles/ # Profile source models
├── component-definitions/ # Component definition source models
├── system-security-plans/ # SSP source models
├── assessment-plans/ # Assessment plan source models
├── assessment-results/ # Assessment results source models
└── plan-of-action-and-milestones/ # POA&M source models
Each model instance lives in its own subdirectory:
catalogs/
└── nist-800-53/
└── catalog.json # The actual OSCAL model file
trestle init creates the workspace. Three modes available:
| Mode | Flag | Creates | Use Case |
|---|---|---|---|
| Full | --full (default) | .trestle/ + dist/ + all model dirs | Full functionality: local models, API, governed docs |
| Local | --local | .trestle/ + all model dirs (no dist/) | Local OSCAL model management only |
| GovDocs | --govdocs | .trestle/ only | Document governance only |
.trestle/ directory contains config files, caches, and templatesdist/ directory holds assembled/merged output files.json) or YAML (.yaml, .yml)The workspace config lives at .trestle/config.ini. It can store task configurations and other settings used by trestle commands.
.trestle/ directorycatalogs/*/catalog.json)trestle validate -a to validate all models