research
Start or resume an academic research project — idea through literature, methodology, writing, feedback, and publishing
Validate AWS CLI, credentials, SES, Route 53, and ACM readiness before deploying infrastructure. Produces a pass/fail report with action items.
> /plugin marketplace add GRCEngClub/claude-grc-engineeringHow it fires
How this command gets triggered: by you, by Claude, or both.
/preflightContext preview
What this command does when you run it.
Validate AWS CLI, credentials, SES, Route 53, and ACM readiness before deploying infrastructure. Produces a pass/fail report with action items.
description: Validate AWS CLI, credentials, SES, Route 53, and ACM readiness before deploying infrastructure. Produces a pass/fail report with action items.
Runs 10 automated checks against your AWS environment to verify everything is ready for deployment. Produces a three-section report: PASS, ACTION AUTOMATED, and ACTION HUMAN (with console links and estimated time for each).
1. AWS CLI installed 2. Node.js v18+ installed 3. npm installed 4. AWS credentials valid (`aws sts get-caller-identity`) 5. Region set to `us-east-1` (required for CloudFront + ACM) 6. CloudFormation template valid 7. SES email verified *(if contact form enabled)* 8. Route 53 hosted zone exists *(if custom domain)* 9. ACM certificate issued in us-east-1 *(if custom domain)* 10. `gh` CLI installed *(for repo/cicd steps)*
/grc-portfolio:preflight ~/Desktop/repos/my-grc-portfolio /grc-portfolio:preflight
Once all checks pass, run `/grc-portfolio:infra` to deploy the AWS infrastructure.
Open-source GRC Engineering resource for Claude. claude-grc-engineering turns technical evidence from cloud, SaaS, code, and security tools into framework-aligned findings, gap reports, remediation guidance, evidence packages, and OSCAL workflows.
Repo: GRCEngClub/claude-grc-engineering
Start or resume an academic research project — idea through literature, methodology, writing, feedback, and publishing
Query AWS for compliance-relevant configuration across IAM, S3, CloudTrail, EBS, and emit findings conforming to the v1 contract.
Install the frdocx-to-froscal-ssp Python pipeline and verify its dependencies. Idempotent.
Retrieve a single AWS Secrets Manager secret value to stdout or a 0600-permission file. Opt-in retrieval mode — never writes to the findings cache.
Run testssl.sh against one or more HTTPS endpoints and emit v1 Findings mapped to SOC 2, NIST 800-53, PCI DSS 4.0.1, ISO 27001, and SCF controls.