| name | team-okrs |
| description | Team operations dashboard template — Linear/Asana-clean hybrid with sprint status hero, 4-segment progress bar, workstream cards, chronological activity stream with colored event badges, right-rail with today's schedule + team-presence + upcoming milestones. For team status snapshots, OKR reviews, "team this week" all-hands views. |
| visibility | public |
| mode | template |
| carrier | web-page |
| scenario | internal-tool |
| pattern_source | activity-stream.html |
| source_priority | skill-first |
| triggers | ["做个团队 OKR 看板","sprint 状态页","团队周会 dashboard","活动流看板","team this week 页","里程碑追踪页"] |
Team OKRs Template
Use this template when the artifact is a team-facing status / OKR / sprint console — not a personal todo, not a public marketing page, not a deck.
Use When
- The audience is a team, lead, or stakeholder reviewing collective progress — quarterly OKR review, sprint status, "this week" all-hands view.
- Surfaces needed: sprint hero with progress segments, workstream cards with owners, chronological activity feed with event types (shipped / blocked / reviewed / commented / uploaded), today's schedule, team presence, upcoming milestones.
- Look should feel like a polished internal tool (Linear / Asana / Notion-flavored), neutral and calm.
Avoid When
- The artifact is a personal todo / planner — too team-centric.
- The artifact is meant to be presented as slides (use a
ppt/ deck template).
- The page is public marketing — wrong audience, wrong density.
- The data is purely analytical (charts, BI metrics) — use
dashboard/ (more chart-oriented) instead.
- The content is a periodic narrative digest with prose — use
Project Brief/ (notebook weekly digest).
Required Reading
Read this SKILL.md first. Do not read activity-stream.html by default.
Read activity-stream.html only when you need: the 4-segment sprint progress bar geometry, the event-badge taxonomy (green check / red alert / purple comment / amber up-arrow / dark review), the workstream-card layout, the schedule current-time indicator, or the team-presence dot pattern. Extract patterns; do not copy placeholder names, project titles, or class names wholesale.
Design Strategy
Decide the page's answer before placing components:
- "Are we on track this sprint?" → hero progress + status stats dominate
- "What did the team do this week?" → activity stream is the spine, hero shrinks
- "What's next?" → workstream cards + milestones dominate
- "Who's around right now?" → presence + schedule dominate
A single page can blend these but pick the lead question.
Design Structure / Visual Weight
The page is a composition of zones with deliberately different visual weight — not a stack of equal rows. Before placing any component, sketch the weight tiers:
- Hero (≈ 30–40% of first screen) — sprint title + 4-segment progress bar + 3–4 status stats. Dominant; answers the lead question immediately.
