name: apple-platform-project-interview description: Use when the Apple workspace setup flow needs project intent, platform targets, personalization, policy, config, CI, MCP, and standardization decisions collected before choosing repo changes.

Apple Platform Project Interview

Run this interview after capability discovery and before workspace choice, installs, or artifact application.

Use this skill when:

Collect, in order:

discovered plugin, project-local skill, subagent, and MCP surface
repo state and detected workspace hints
project purpose and delivery shape
Apple platform targets
workspace shape confirmation
if Xcode, project strategy confirmation
priority technologies
repo and team policy
package README inputs when the repo is package-first
app README inputs when the repo is app-first
Agent Personalization
optional tooling, .codex/config.toml, official multi-agent runtime, optional MCP, and SFSafeSymbols

Always ask which communication language should be fixed in AGENTS.md.
If the user does not choose one, use Use the language the client used to contact the agent.
Keep the strict-quality baseline for pushback, quality, long-term priority, temporary-fix policy, and risk disclosure unless the user explicitly changes them.

Keep this order exact:

ask whether the repo should carry .codex/config.toml
if yes, ask whether the standard setup / review / release profiles should be used
ask whether official multi-agent runtime should be enabled
if runtime is enabled, ask separately whether to continue into project-local subagent selection
if runtime is not enabled, ask separately whether project-local subagents are still desired directly

Produce enough information to finalize:

Do not choose skills, subagents, MCP, or repo files before the interview is complete.
For existing_structured_repo, confirm detected choices instead of asking from a blank slate.
Derive README facts from repo evidence when available instead of asking every question directly.