Menü
Use when repository-owned work needs an approved implementation plan written from an approved design or reviewed retained spec.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
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.
| name | internal-gateway-writing-plans |
| description | Use when repository-owned work needs an approved implementation plan written from an approved design or reviewed retained spec. |
/superpowers-writing-plans: required owner for producing the retained plan./internal-gateway-execute-plans: required next owner after human review and
explicit execution approval.superpowers-* maintenance to their existing owners./superpowers-writing-plans and produce one reviewable retained plan
under tmp/superpowers/plans/ with ordered actionable tasks, concrete file
targets, focused validation, and an execution handoff. Completion: one plan
exists at the retained path and contains those four artifact properties plus
one versioned ## Execution Contract fenced JSON object./internal-gateway-execute-plans as
the next owner, and wait for explicit execution approval. Completion: the
path and next owner are reported and execution has not started without
approval.rtk, graphify, or another optional accelerator a prerequisite
or command prefix unless the task's actual subject is that tool.The executor owns the single mechanical plan validator. Do not add a
writer-local validator, draft-only lifecycle, or duplicate parser contract.
Before handoff, run the executor-owned preflight against the written plan and
revise it until there are zero blocking findings. Plans without the versioned
contract are not actionable.
git add, git commit, git push, or another Git mutation while
writing or handing off a plan. Retained artifacts stay uncommitted for user
review unless the user explicitly requests commit help./internal-gateway-execute-plans and waits for
explicit approval.git diff --check and confirm no Git mutation occurred.