菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Architect produces a full web-app system design from the approved product vision and prototype (the **Design** phase of the spec-driven loop) — extracted architecture drivers, deep exploration of each load-bearing (one-way-door) decision weighed against those drivers, ADRs (architecture style, framework, DB, auth, rendering strategy, multi-tenancy), C4 context/container diagrams, data model, API contracts, component breakdown, observability + security plan, technical verification criteria that bind back to the vision's product criteria, and a phased implementation plan. Use after product vision and prototype are approved.
Architect decomposes the approved web-app system design into milestones and INVEST-sized tasks, splitting each feature slice into a backend task (API + business logic + data, test-driven) and a dependent frontend task (the UI that consumes it), with acceptance criteria, dependencies, and a parallelization plan (the **Tasks** phase of the spec-driven loop). Each task declares its discipline and which system-design verification criteria it advances, so the spec→implementation lineage is explicit. Starts with a walking skeleton (real, deployable, end-to-end). Use after system design is approved.
DBA designs the database schema for a web application from the system design — tables, indexes, constraints, RLS, zero-downtime migration plan. Defaults to Postgres + Redis. Produces .claude/database-schema.md. Use after system design is approved.
Designer extracts a web design specification from the approved HTML prototype — design tokens (CSS custom properties for color/type/spacing/radius/shadow), component inventory, screen map with visual acceptance criteria per screen, responsive behavior, and interaction states. This becomes the single source of truth for UI implementation. Use after the prototype is approved.
Project kickoff — CEO has a natural conversation with the client, plays devil's advocate, crystallizes the product vision (the **Specify** phase of the spec-driven loop) with explicit verification criteria, then iterates with the designer on visuals until approved. No implementation details — pure product thinking. Use at the very start of a new project.
CEO runs the task execution cycle — picks the next task, routes it to the backend engineer (test-driven) or the frontend engineer (UI) by its discipline, confirms the engineer's self-reviewed work (tests green; designer + ux-engineer for UI), and marks it done. Updates task status in .claude/tasks/. Repeats until milestone is complete. Use when ready to start building.
| 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] |
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.
Read these files (if they exist):
.claude/ceo-brain.md — your knowledge base.claude/product-vision.md — the product visionCLAUDE.md — project contextIf --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.
Send researcher to sweep whatever exists:
git log --oneline -30 — recent directionCompare what exists NOW against your knowledge base and product vision:
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:
Based on the conversation and findings:
.claude/product-vision.md — if scope, flows, or priorities changed (CEO edits directly).claude/ceo-brain.md — fresh state, new decisions, updated risks (CEO edits directly)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)CEO never draws diagrams or writes Project Context — those are delegated.
Give the client a 3-5 line summary: