assess-pci
Conduct a PCI-DSS scope assessment and compliance review for payment card handling.
What this skill does
# PCI-DSS Compliance Assessment
Conduct a comprehensive PCI-DSS scope and compliance assessment.
## Workflow
### Step 1: Load Required Skills
Load these skills:
- `pci-dss-compliance` - PCI requirements and SAQ guidance
- `security-frameworks` - Security control mapping
- `data-classification` - Cardholder data identification
### Step 2: Spawn Security Auditor Agent
Spawn the `security-auditor` agent with the following prompt:
```text
Conduct a comprehensive PCI-DSS compliance assessment for: $ARGUMENTS
Perform the following assessments:
1. Scope Determination
- Identify all cardholder data flows
- Map the Cardholder Data Environment (CDE)
- Identify connected systems
- Evaluate scope reduction opportunities
2. SAQ Selection
- Determine appropriate SAQ type
- Validate SAQ eligibility
- Identify any disqualifying factors
3. Scope Reduction Analysis
- Tokenization opportunities
- P2PE eligibility
- Hosted payment page options
- Network segmentation assessment
4. Requirement Assessment (12 Requirements)
- Req 1-2: Network security
- Req 3-4: Cardholder data protection
- Req 5-6: Vulnerability management
- Req 7-9: Access control
- Req 10-11: Monitoring and testing
- Req 12: Security policies
5. Gap Analysis
- Compare current state to PCI DSS 4.0
- Identify non-compliant controls
- Prioritize by risk and deadline
6. Evidence Assessment
- Review documentation
- Assess scanning/testing evidence
- Identify evidence gaps
Provide a complete PCI-DSS assessment with:
- Scope diagram and boundaries
- SAQ recommendation with justification
- Requirement-by-requirement assessment
- Prioritized remediation plan
```
### Step 3: Generate Assessment Report
Ensure the report includes:
- Executive summary with compliance status
- Scope diagram
- SAQ recommendation
- Detailed requirement assessment
- Remediation roadmap with PCI 4.0 deadlines
## Example Usage
```bash
# Assess an e-commerce checkout
/compliance-planning:assess-pci "e-commerce checkout using Stripe Elements"
# Assess a retail POS system
/compliance-planning:assess-pci "retail point-of-sale with P2PE terminals"
# Assess a payment gateway integration
/compliance-planning:assess-pci "custom payment processing with direct API integration"
```
## Output Format
````markdown
# PCI-DSS Assessment: [System Name]
## Executive Summary
### SAQ Type: [A / A-EP / B / B-IP / C / C-VT / D / P2PE]
### Overall Compliance: [COMPLIANT / PARTIAL / NON-COMPLIANT]
| Requirement | Status | Priority |
|-------------|--------|----------|
| 1. Network Security Controls | [Status] | [Priority] |
| 2. Secure Configuration | [Status] | [Priority] |
| ... | ... | ... |
| 12. Security Policies | [Status] | [Priority] |
---
## Scope Assessment
### Cardholder Data Flow
```mermaid
flowchart LR
Customer --> Website --> PaymentAPI --> Processor
```
### CDE Boundaries
| System | In Scope | Reason |
|--------|----------|--------|
### Scope Reduction Opportunities
| Opportunity | Effort | Impact | Recommendation |
|-------------|--------|--------|----------------|
---
## SAQ Determination
### Recommended SAQ: [Type]
**Justification:**
[Why this SAQ applies]
**Eligibility Confirmation:**
- [ ] Criterion 1
- [ ] Criterion 2
---
## Requirement Assessment
### Requirement 1: Network Security Controls
| Sub-Req | Description | Status | Evidence | Gap |
|---------|-------------|--------|----------|-----|
[Continue for all 12 requirements]
---
## Gap Analysis
### Critical Gaps (Block Compliance)
| Gap | Requirement | Current State | Required State | Deadline |
|-----|-------------|---------------|----------------|----------|
### High Priority Gaps
| Gap | Requirement | Current State | Required State |
|-----|-------------|---------------|----------------|
---
## PCI DSS 4.0 Timeline
| Requirement | Status | Deadline | Action Required |
|-------------|--------|----------|-----------------|
---
## Remediation Roadmap
### Phase 1: Critical (Blocks Compliance)
1. [Action with owner and deadline]
### Phase 2: High Priority
1. [Action]
### Phase 3: Best Practices
1. [Action]
---
## Validation Requirements
- [ ] Quarterly ASV scans
- [ ] Annual penetration test
- [ ] Annual SAQ completion
- [ ] [Other requirements]
````
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.