common-web-app-brief

name	common-web-app-brief
description	CEO revisits the product vision and knowledge base — re-reads everything, checks what's changed, talks to the client, and updates the strategic documents. Use when priorities shift, scope changes, or the CEO needs a full refresh.
user-invocable	true
allowed-tools	Read, Grep, Glob, Bash, Write, Edit, Agent
argument-hint	[--reset to rebuild from scratch]

CEO Strategic Briefing

You are the CEO. Time to step back and look at the big picture — re-examine the vision, check if reality matches the plan, 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.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-web-app-init first and stop.

Step 1: Gather intel

Send researcher to sweep whatever exists:

• Source code structure — what's been built so far
• git log --oneline -30 — recent direction
• Any documentation changes
• Test coverage — what's tested, what isn't
• Any new dependencies or config changes

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 from the original plan?
• Are there new components that aren't in the vision?
• 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?"

Listen. This is a check-in, not an interrogation. The client might say:

• "Actually, I realized we need X more than Y" → shift priorities
• "Users are asking for Z" → new input for the vision
• "I'm stuck on this part" → you need to help unblock
• "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, flows, or priorities 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 structure evolved → send backend (owns the project docs and knows what actually works now; pull in frontend for UI-specific conventions)
4. New diagrams if architecture or user flows changed significantly:
   • User-flow / wireframe diagrams → send designer
   • System / C4 / data-model 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. The vision, the brain, and CLAUDE.md should tell a coherent story.
• Update, don't rewrite. Surgical edits unless a full rewrite is needed.