writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
Use when you have a spec or requirements for a multi-step task, before touching code
Guide for setting up Claude Code infrastructure in new or existing projects
Analysis phase for /health-check command - scores each component
Complete end-to-end Android Play Store deployment pipeline setup in one command
Verify release readiness by detecting changed skills, checking version updates, and running validation scripts. Use before creating releases or publishing to marketplace.
Use when you have a spec or requirements for a multi-step task, before touching code
Runs validation checks and gating tasks to ensure artifacts meet strict-mode requirements and quality standards.
Execute detailed plans in batches with review checkpoints
Harden code and pipelines for production. Use when the user asks for production-ready code, hardening, release readiness, performance, monitoring, or reliability.
Workflow E2E multi-repo: targets → snapshot → implement → no-any + ci → E2E_TRACE → review → wrap.
Use when completing tasks, implementing major features, or before merging to verify work meets requirements - dispatches superpowers:code-reviewer subagent to review implementation against plan or requirements before proceeding
GitHub Actions CI/CD, Terraform 인프라, Docker Compose 로컬 환경, AWS SSM 포트포워딩. 시크릿 하드코딩 금지, 환경 분리 필수. /kb-devops 명령 시 자동 활성화.
CI/CD, deployment, monitoring ve infrastructure setup için kullanılır. GitHub Actions, Vercel, Sentry ve performance monitoring konularında uzman.
Use when working with Ansible Core 2.19 for automation, configuration management, playbooks, modules, or infrastructure as code (project)
Use when executing implementation plans - dispatches fresh subagent per task with two-stage review process (spec compliance then code quality)
EAS Build configuration for iOS and Android. Use when setting up cloud builds.
Enforce Sketch Magic dev-readiness gates. Use when asked “are you done?”, when dev server errors appear, when proof video is required, or when verifying compile/lint/test/dev-smoke status.
Review implementation work at checkpoints during plan execution. Use when verifying phase completion, validating code changes, or performing final plan review.
Target-agnostic bug bounty hunting methodology with parallel recon, systematic testing workflows, and vulnerability-specific exploitation guidance
Validates compliance with 9 Constitutional Articles and Phase -1 Gates before implementation. Trigger terms: constitution, governance, compliance, validation, constitutional compliance, Phase -1 Gates, simplicity gate, anti-abstraction gate, test-first, library-first, EARS compliance, governance validation, constitutional audit, compliance check, gate validation. Enforces all 9 Constitutional Articles with automated validation: - Article I: Library-First Principle - Article II: CLI Interface Mandate - Article III: Test-First Imperative - Article IV: EARS Requirements Format - Article V: Traceability Mandate - Article VI: Project Memory - Article VII: Simplicity Gate - Article VIII: Anti-Abstraction Gate - Article IX: Integration-First Testing Runs Phase -1 Gates before any implementation begins. Use when: validating project governance, checking constitutional compliance, or enforcing quality gates before implementation.