cloud-strategy.github

Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.

Use when creating, reviewing, or materially revising a repository-owned Copilot agent under `.github/agents/`.

Use when /internal-aws selects the AWS governance lane for IAM operating models, trust policies, federation, permission boundaries, SCPs, tag policies, exception controls, or access guardrails.

Use when /internal-aws selects the AWS Lambda lane for handlers, event sources, runtimes, packaging, retries, concurrency, cold starts, or Lambda-specific configuration.

Use when /internal-aws selects the AWS research lane to retrieve current official AWS documentation, regional availability, service behavior, IAM state, or policy-simulation evidence.

Use when /internal-aws selects the AWS operations lane for monitoring, logging, rollout validation, backup and restore proof, DR evidence, reporting, or audit evidence.

Use when /internal-aws selects the AWS organization-structure lane for Organizations, accounts, OUs, delegated administrators, StackSets topology, or platform-level network placement.

Use first for every AWS request. Classify the primary deliverable and invoke the minimum specialist lane for AWS structure, governance, operations, Lambda, current documentation or IAM evidence, strategic decisions, or cost optimization.

Use when /internal-aws selects the AWS strategic lane for option comparison, multi-lens tradeoffs, cost-value analysis, blast radius, or reversibility before implementation.

Use when /internal-azure selects Azure DevOps pipeline YAML, project automation, triggers, environments, approvals, or artifact-flow work.

Use when /internal-azure selects Azure authorization, workload identity, privileged access, Policy, guardrail, or exception work.

Use when /internal-azure selects Azure preflight, observability, rollout evidence, backup/restore proof, continuity validation, or operational reporting.

Use when /internal-azure selects Azure hierarchy, subscription, landing-zone, residency, or platform-topology work.

Azure platform entry point that selects the specialist for the user's immediate deliverable.

Use when /internal-azure selects explicit Azure decision framing, tradeoff analysis, or proportional multi-lens support.

Use when creating, reviewing, or modifying standalone Bash or POSIX `sh` scripts, utilities, wrappers, launchers, or other operator-facing shell entrypoints.

Use when creating, analyzing, reviewing, or modifying embedded Bash or POSIX `sh`, sourced shell helpers, or non-operator shell fragments that need dialect, safety, quoting, parser, or validation guidance.

Use when deciding whether a complex domain needs Domain-Driven Design, framing the current DDD stage from strategic modeling through tactical and evented patterns, and producing only the artifacts justified by real domain pressure.

Use when a bug, test failure, build failure, validator drift, sync failure, or unexpected behavior needs a reproducible root-cause diagnosis before a fix.

Use when a repository-owned plan, proposal, or decision needs a critical challenge, pre-mortem, hidden-assumption test, failure-mode analysis, or lateral reframe before action.

Use when executing or resuming an approved repository-owned retained plan under tmp/superpowers/plans/.

Use when a repository-owned idea needs brainstorming, assumption challenge, alternative discovery, critical resolution, and an automatic handoff to implementation planning.

Use when a concrete low-to-medium-risk repository-owned coding or non-coding task can be completed quickly in one bounded run.

Use when repository-owned work needs an approved implementation plan written from an approved design or reviewed retained spec.

Use when /internal-gcp selects governance for Google Cloud IAM, workload identity, service-account boundaries, Org Policy, inherited guardrails, or governed exceptions.

Use when /internal-gcp selects operations for Google Cloud monitoring, logging, backup, restore, recovery validation, asset inventory, rollout evidence, or operational reporting.

Use when /internal-gcp selects organization structure for Google Cloud org or folder layout, billing-account ownership, project segmentation, Shared VPC topology, environment boundaries, or regional placement.

Route any Google Cloud request to organization structure, governance, operations, or strategic decision support. Use internal-gcp as the official and default GCP entry point for scoped, ambiguous, or cross-domain work.

Use when /internal-gcp selects strategic decision support for a Google Cloud decision, assumptions, realistic options, tradeoffs, reversibility, or a recommendation before implementation.

Use when /internal-github routes composite-action work under `.github/actions/`, including inputs, outputs, shell safety, tests, documentation, and compatibility.

Use when /internal-github routes GitHub Actions workflow authoring or debugging under `.github/workflows/`, including `workflow_call` and reuse-pattern selection.

Use when /internal-github routes a GitHub governance decision covering rulesets, permissions, Apps, Actions permissions, OIDC trust, secrets, environments, CODEOWNERS, or Copilot policy.

Use when /internal-github routes a GitHub operational request covering Actions health, runners, audit evidence, reporting, drift, preflight, rollout validation, or post-rollout proof.

Use when /internal-github routes pull-request lifecycle work covering creation, body updates, readiness, reviews, merge, or terminal-state verification.

Official entry point for any GitHub task. Routes every GitHub request to the right specialist - governance, operations, Actions workflows, composite actions, PR lifecycle, or Copilot platform research - or to /internal-github-strategic for high-level decision framing. Use for any GitHub request, scoped or ambiguous.

Use when /internal-github routes a GitHub platform or operating-model decision that requires option comparison, tradeoff analysis, or multi-lens strategic framing.

Use when framework-neutral Java application or library design is the primary concern, including module, package, domain, API, collaborator, concurrency, unit-test, or contract-test boundaries. Do not use for isolated language-level source changes, generic build metadata, or framework-managed wiring and runtime behavior.

Use when Java language or source correctness, readability, resource handling, error behavior, or generic Maven/Gradle build metadata is the primary concern, including compiler release, toolchains, plugins, dependencies, reproducibility, and focused build validation. Do not use when module or domain design, API and concurrency architecture, or framework-managed runtime behavior determines correctness.

Use when Spring Boot-specific framework or runtime semantics determine correctness, including parent, plugin, BOM, starter, auto-configuration, bean wiring, configuration binding, HTTP or data adapters, scheduling, transactions, test contexts, service connections, or virtual-thread enablement. Do not use for ordinary Java source work, generic Maven/Gradle metadata, or framework-neutral application and library design.

Use when editing or reviewing Makefile or .mk syntax, targets, prerequisites, recipes, variables, or static format checks.