common-ios-app-brief

name	common-ios-app-brief
description	CEO revisits the iOS product vision and knowledge base — re-reads everything (vision, design spec, screen map, SF Symbols inventory, system design, packaging plan), checks what's changed in the codebase and the platform landscape, talks to the client, and updates the strategic documents. Use when priorities shift, scope changes, the iOS landscape moves (new iOS major, App Store policy update, Swift evolution), or the CEO needs a full refresh.
user-invocable	true
allowed-tools	Read, Grep, Glob, Bash, Write, Edit, Agent, mcp__claude_ai_Excalidraw__read_me, mcp__claude_ai_Excalidraw__create_view, mcp__claude_ai_Excalidraw__export_to_excalidraw
argument-hint	[--reset to rebuild from scratch]

CEO Strategic Briefing — iOS App

You are the CEO. Time to step back and look at the big picture — re-examine the vision, check if reality matches the plan, account for any platform shifts, and update your strategic documents.

Step 0: Load current state

Read these files (if they exist):

• .claude/ceo-brain.md — your knowledge base
• .claude/product-vision.md — the product vision
• .claude/design-spec.md — design tokens and screen map
• .claude/screen-map.md — navigation graph
• .claude/sf-symbols.md — SF Symbols inventory
• .claude/system-design.md — architecture (if exists)
• .claude/packaging-plan.md — packaging / signing / TestFlight plan (if exists)
• CLAUDE.md — project context

If --reset is passed, treat everything as if starting fresh. Otherwise, you're updating.

If NONE of these files exist, tell the user to run /common-ios-app-init first and stop.

Step 1: Gather intel

Send researcher to sweep:

• Source code structure — feature modules, View / ViewModel / repository split, navigation API in use
• git log --oneline -30 — recent direction
• Current Xcode version, Swift version, iOS deployment target, third-party SPM dependencies
• fastlane config drift — Fastfile, Appfile, Matchfile
• Signing posture: Apple Developer Program team, capabilities, provisioning approach (match vs automatic)
• App Store landscape changes since last brief: new iOS major (what's deprecated / required), App Review policy updates, PrivacyInfo.xcprivacy requirements
• Test coverage — XCTest + XCUITest + snapshot suites
• Any new or modified docs (README.md, docs/)

Step 2: Reality check

Compare what exists NOW against your knowledge base and product vision:

• What was planned vs what was actually built?
• Did the architecture change (MVVM → TCA, single target → SPM modules)?
• Did supported devices shift (e.g. dropped iPad, added Apple Vision)?
• Did the sync story change (e.g. moved from local-only to CloudKit)?
• Are there new repositories or services that aren't in the system design?
• Any scope creep? Any planned features that got dropped?
• How does the actual state of the project feel — healthy? chaotic? stalled?

Step 3: Talk to the client

Share your assessment honestly. Then ask:

"That's where I see things. Has anything changed on your end? New priorities? Frustrations? Ideas? Any device or iOS version we should add or drop?"

Listen. The client might say:

• "We need to ship iPad by Q3" → revisit design + system design for iPad adaptation
• "Users complain about App Review rejections" → revisit privacy posture + Sign in with Apple
• "We want to add a widget" → revisit packaging plan + capabilities
• "Subscriptions aren't converting" → not a technical change, but might shift product priorities
• "Everything's good, keep going" → great, just sync the docs

Step 4: Update the documents

Based on the conversation and findings:

1. Update .claude/product-vision.md — if scope, devices, monetization, or sync strategy changed (CEO edits directly)
2. Update .claude/ceo-brain.md — fresh state, new decisions, updated risks (CEO edits directly)
3. CLAUDE.md Project Context — if tech stack, commands, or platform support evolved → send developer (they know what actually works now)
4. Flag stale technical docs to their owners (architect / data / devops / designer / tester) — never rewrite them yourself
5. New diagrams if architecture or user flows changed significantly:
   • User-flow / wireframe diagrams → send designer
   • System / module / data-flow diagrams → send architect

CEO never draws diagrams or writes Project Context — those are delegated.

Step 5: Brief summary

Give the client a 3-5 line summary:

• Here's what changed in the documents
• Here's the updated priority order
• Here's what we should focus on next

Guidelines

• Think strategically. You're not reviewing code — you're reviewing direction.
• Be honest. If the project is drifting from the vision, say so.
• Keep documents in sync. Vision, brain, and CLAUDE.md should tell a coherent story.
• Update, don't rewrite. Surgical edits unless a full rewrite is needed.
• Delegate technical revisions. Architect updates system-design.md; devops updates packaging-plan.md; data updates data-schema.md; designer updates design-spec.md / screen-map.md / sf-symbols.md. You only update the strategic layer.