DevSecOps Architecture Account Migration Checklist

Role: Enterprise Solutions Architect specializing in CI/CD pipeline security and static application security testing (SAST).

Context

• Client Name: {{client_name}}
• Legacy Debugging & Linting Stack: {{legacy_debug_stack}}
• CI/CD Orchestrator: {{pipeline_orchestrator}}
• Compliance Mandates: {{compliance_framework}}
• Active Repository Volume: {{repo_volume}}
• Developer Friction Points: {{developer_friction_points}}

Task

Produce an account plan migration checklist to consolidate {{client_name}}'s fragmented code analysis tools into an enterprise DevSecOps and automated code debugging platform.

Method

1. Analyze compatibility between {{pipeline_orchestrator}} and modern automated code inspection engines.
2. Review vulnerabilities and blind spots inherent in {{legacy_debug_stack}} across {{repo_volume}} active repositories.
3. Address developer workflow bottlenecks captured in {{developer_friction_points}} to minimize false-positive fatigue.
4. Align scanning policies with regulatory expectations defined in {{compliance_framework}}.
5. Define gating criteria for pull-request debugging checks without degrading pipeline throughput.
6. Establish key account stakeholder milestones spanning AppSec leads, Staff Engineers, and VP of Engineering.
7. Structure a migration readiness checklist covering technical, organizational, and executive approval gates.

Constraints

• Focus strictly on code-level security, pipeline integration, and automated debugging.
• MUST use markdown checkbox syntax [ ] for all checklist items.
• MUST NOT prescribe generic IT service management processes outside CI/CD and software development.
• Keep all action items specific to developer productivity and code security.

Output format

• Pipeline & Repo Audit Phase (5-6 checkbox items)
• Security Policy & Rule Standardization Phase (5-6 checkbox items)
• Developer Enablement & Pilot Phase (4-5 checkbox items)
• Executive Account Review & Sign-Off Phase (3-4 checkbox items)

Self-review

• Checked that all context variables are explicitly incorporated into the reasoning steps.
• Ensured the checklist directly resolves the friction points outlined in {{developer_friction_points}}.
• Verified every section uses valid markdown task list formatting.