1) Intake + outcome definition (what the rituals are for)
1) 信息收集 + 目标定义（仪式的核心目的）
Inputs: user context; references/INTAKE.md.
Actions: Clarify the top 2–3 outcomes (e.g., alignment, decision speed, execution reliability, learning). Set constraints (time budget, remote/async needs). Define what “good” feels like in 4–6 bullets.
Outputs: Context snapshot + outcome list + constraints.
Checks: You can explain the “why” in one sentence (“We’re doing this to ____ without ____.”).
Inputs: current meeting list/cadence; pain points.
Actions: Build a ritual inventory table. For each ritual: purpose, participants, cadence, outputs, and whether it’s working. Identify duplicates and “status-only” meetings.
Outputs: Ritual inventory audit with a keep/change/kill recommendation.
Checks: Every existing ritual has an explicit purpose and output; “kill” items have a replacement or rationale.
3) Design rules + time budget (make it a system, not meetings)
3) 设计规则 + 时间预算（打造系统而非零散会议）
Inputs: outcomes + audit.
Actions: Define a small set of design rules (named, templated, artifact-first, owner-driven, async-by-default). Establish a weekly meeting time budget and decide what must be synchronous vs async.
Outputs: Ritual design principles + time budget + naming scheme.
Checks: Total sync time stays within budget; each ritual has an owner and an artifact output.
Actions: Propose 3–7 Golden Rituals that cover: alignment, decisions, execution, learning, and belonging (as needed). Name them with memorable, team-relevant names.
Outputs: Golden Rituals shortlist + mapping table (ritual → outcome).
Checks: Each Golden Ritual earns its slot; no “nice-to-have” meetings.
5) Write ritual specs + templates (make them repeatable)
5) 撰写仪式规范 + 模板（实现可复用）
Inputs: Golden Rituals shortlist; references/TEMPLATES.md.
Actions: For each Golden Ritual, produce a spec: purpose, cadence, roles, agenda/format, prep, outputs, follow-ups, and anti-patterns. Create the corresponding agenda/notes template.
Outputs: One “Ritual Spec” per Golden Ritual + copy/paste templates.
Checks: Rituals are Named and Templated; outputs are explicit (decisions, priorities, action list, learnings).
6) Make them “Known by first Friday” (onboarding + rollout)
6) 实现「第一周周五前熟知」（入职 + 推广）
Inputs: Ritual specs; onboarding constraints.
Actions: Create a 1-page onboarding primer and a rollout plan: pilot order, comms, calendar creation, where templates live, and how new hires learn the rituals in week 1.
Outputs: Onboarding primer + rollout plan.
Checks: A new hire can find the rituals, understand purpose, and run one using templates by their first Friday.
Actions: Define governance: ritual owners, quarterly review, feedback loop, and retirement rules. Run references/CHECKLISTS.md and score with references/RUBRIC.md. Add Risks / Open questions / Next steps.
Outputs: Final Team Rituals Pack.
Checks: The pack is minimal, adoptable, and has a way to evolve without ritual sprawl.
Example 1 (fix chaotic cadence): “We’re a 12-person product+engineering team (remote across PST/EST). Meetings feel random and we keep missing decisions. Design Golden Rituals, write templates, and create a first-Friday onboarding primer.”
Expected: a small set of named rituals with templates, mapped to outcomes, plus rollout + governance.
Example 2 (new manager operating system): “I’m inheriting a team of 7 ICs with low accountability and unclear priorities. Create a weekly operating cadence with minimal meetings and clear artifact outputs.”
Expected: ritual inventory audit + a minimal Golden Rituals set + artifact-first templates.
Boundary example: “Fix our company culture.”
Response: ask what specifically is broken and at what scope; propose a small team-level ritual system only, or suggest doing values/strategy/org work first.