Turning client onboarding into a repeatable plan
A three-tab workbook and a chain of Claude skills that answer the same three questions for every new FedRAMP 20x client.
Every new FedRAMP 20x client I work with starts with the same three questions. Which KSIs do their capabilities cover? Which systems do we need to connect, and with what access? Which validators will prove it to an assessor? Answering them by hand was slow, and the result looked different every time.
So I built a fetcher plan: a workbook with three tabs, and a set of Claude skills that fill it from the client's Solution Capability export.
Systems
One row per source system the client's capabilities imply. It lists the API surface, how authentication works, the read-only permissions to request, which existing fetchers already cover it, and what still needs to be built. The permissions column is written so it can go straight into an access request.
Coverage
One row per capability and KSI pair. The KSI statement is copied word for word from fedramp.gov, so the client and the assessor are reading the same sentence.
Each row gets one of four verdicts: covered, partial, not covered, or not automatable. That last one matters. Some indicators are better proven by a policy or an attestation, and the plan should say so instead of promising a fetcher.
Validators
For each evidence set, a small group of validators covering completeness, configuration, and integrity. Every row has a regex with named groups, a pass rule, a plain statement written from an assessor's point of view, and a column for what the validator does not prove. That last column gets asked about more than any other.
evidence_set: entra_conditional_access
validator: MFA required for all privileged roles
kind: configuration
polarity: must_match
anchor_field: summary.privileged_roles_without_mfa
regex: "privileged_roles_without_mfa":\s*(?<gap>\d+)
rule: gap == 0
statement: Every privileged directory role is covered by an
enabled Conditional Access policy requiring MFA.
does_not_prove: That break-glass accounts are monitored.Why a chain of skills
The tabs depend on each other, so an orchestrator skill always runs them in the same order: systems, then coverage, then validators. What comes out is a first draft a person reviews, not a final answer. The first client I ran it for was on Azure Government, and we started from a reviewable plan instead of a blank spreadsheet.