Skip to content

Prompt guide

Complete the quickstart, select the owning main agent, and state the intended scope. A prompt example does not authorize cloud changes or bypass a required review.

Use the current roster. The body-migration candidate lets Orchestrator dispatch approved main workers; the owner can also select main agents directly. One planner handles both tracks. CodeGen and Deploy have separate Bicep and Terraform agents. 10-Challenger is human-selected for optional manual review. The shared-review candidate uses the read-only challenger-review-subagent for automatic and optional manual reviews. See the review contract and pending runtime evidence.

Skills provide reusable instructions. Their flags control automatic selection and slash-menu visibility; they do not grant tools or permissions. Consult the pinned Explorer and your checkout’s SKILL.md files.

Published site writing belongs to apex-docs and its checked-in unslop skill. The historical product apex-docs-writer is retired.

Allowed parents call bounded helpers for pricing, validation, or previews. A helper’s result is evidence to evaluate, not approval to continue automatically. See the helper reference.

Local .prompt.md files adapt shared procedures to VS Code. Check configured discovery locations and the actual prompt file. Attaching text does not select its intended main agent automatically.

Host entries are separate manual skills. Select the owner first and verify runtime support. Static discovery tests cannot establish model entitlement or successful execution in another client.

Use workflow prompts for current examples. For resume, the Local adapter is /apex-resume-workflow; the Host entry is apex-host-workflow-start with an explicit resume operation.

Use the repository prompt reference for commit and debug-log operations. These are separate from workflow start/resume. Retired docs-gardening adapters and branch-specific Sensei tooling are not normal main-branch setup requirements.