Results for “standup”

Your team has high autonomy — and standups are vague, weekly meetings drift into status reports, and 1:1s produce nothing but "I'm fine." This playbook fixes all three layers at once. What's inside: • Daily Standup system — 3-field format, good sample, 4 COO principles to keep it honest • Weekly Meeting — strict 25-min agenda, Scrum Master rotation, 0–10 pulse check • 1:1 Framework — 9-dimension quantified pulse, 5-group deep question bank, bilateral feedback structure • Diagnostic layer — "stuck-at" detection: info / authority / collaboration / capability / direction • FAQ for 4 common failure modes (dead standups, status-report meetings, "I'm fine" 1:1s, scaling beyond 10 people) 🇨🇳 你的团队自由度很高——但 standup 越来越糊，例会变成汇报，1:1 问不出真话。这套三层 Motivation 操作手册解决的正是这件事：standup 是信息层，例会是对齐层，1:1 是个人层。三件事做好了，motivation 不是管出来的，是长出来的。 🇯🇵 チームの自律性は高いのに、スタンドアップは曖昧で、週次ミーティングは進捗報告になり、1on1では「大丈夫です」しか返ってこない——このプレイブックは、その3層すべてを同時に解決します。 🇰🇷 팀의 자율성은 높은데 스탠드업은 두루뭉술하고, 주간 회의는 진척 보고가 되어버리고, 1:1에서는 진심을 들을 수 없다면 — 이 플레이북이 세 레이어 모두를 동시에 해결합니다. Triggers: "团队 motivation" | "standup 没人写" | "例会变成汇报" | "1:1 问不出真话" | "高自由度团队管理" | "COO 如何管人" | "team motivation" | "standup best practices" | "1on1 framework" | "weekly meeting template" | "チームモチベーション" | "팀 동기부여" | "AI startup team ops" | "remote team alignment" | "engagement下降"

The English summary is being prepared. Showing the original description.

Turn recent work or rough notes into a concise daily standup update organized by yesterday, today, and blockers. Connected tools can supply commits, pull requests, ticket changes, and relevant discussions to help assemble the report.

• Preparing a concise daily standup update
• Turning rough work notes into a shareable report
• Summarizing commits, pull requests, and ticket changes

Turn recent work or rough notes into a concise daily standup update organized by yesterday, today, and blockers. Connected tools can supply commits, pull requests, ticket changes, and relevant discussions to help assemble the report.

• Preparing a concise daily standup update
• Turning rough work notes into a shareable report
• Summarizing commits, pull requests, and ticket changes

Compile the team's REAL updates into one async standup — pull what people posted in Slack (and moved in Notion/Linear), not a template for running standups. Use when asked to compile today's standup, pull the team's updates into one post, what did the team ship, or run async standup in Cowork. Reads a Slack channel and (optionally) the tracker via connectors, groups updates by person into shipped / in-progress / blocked, surfaces the blockers needing attention, and produces a standup-digest artifact ready to post back.

The English summary is being prepared. Showing the original description.

Team standup board (Busabase App-in-Skill) for team leads. Use when the user invokes $kelly-standup or /kelly-standup, or asks for standup, daily standup, 晨会, daily check-in, team status board, 团队日报, blockers, who's working on what, team digest, check-in streaks, missing check-in reminders, or collecting async updates from Slack/WeCom/Discord/WhatsApp/docs into one board.

The English summary is being prepared. Showing the original description.

Combine Lark calendar events and unfinished tasks into a daily or weekly briefing. Review meetings in time order, spot scheduling conflicts and free slots, and check task deadlines before starting work or joining a standup.

• Reviewing today's schedule and unfinished tasks
• Checking tomorrow's meetings and task deadlines
• Preparing a morning standup briefing

A standup or status update built from the coding-agent sessions Cognee recorded — prompts, tool calls, edited files, what was left open — per project. Use only when the user explicitly asks for a standup, a status update, a catch-up on their own recent sessions ("what did I work on yesterday / this week"), or asks for the `cognee-standup` skill by name. Not for questions about code, files or the current task.

The English summary is being prepared. Showing the original description.

Full daily team standup across all 6 verticals: Sales, Social Media, Content, SEO, Creative, and Strategy. Spawns all vertical agents in parallel, collects reports, and presents a unified standup summary. Run at 9 AM daily.

The English summary is being prepared. Showing the original description.

Combine today's calendar meetings and open tasks into a summary for a daily team check-in. Review the results as JSON, a table, YAML, or CSV without changing calendar or task data.

• Prepare a summary for a daily team check-in
• Review today's meetings alongside open tasks
• Get a daily summary in table or JSON format

Turn feature requirements into a PRD, a document defining what to build, then organize development plans and GitHub Issues. Coordinate parallel agents and track progress, blockers, and next priorities through delivery.

• Define feature requirements and scope in a PRD
• Split development plans into tasks and sync them to GitHub
• Coordinate parallel agents working on issues

Turn bundled Paperclip issues, comments, and documents into readable wiki updates covering project purpose, current progress, decisions, risks, and next actions, while preserving existing knowledge and citing the supporting activity.

• Summarizing recent project activity in a wiki
• Building wiki pages from historical project activity
• Recording decisions and their supporting evidence

Refresh an LLM Wiki index against the pages that actually exist. Add missing entries, remove entries for deleted pages, preserve custom categories, and log change counts while leaving page bodies untouched.

• Add existing pages missing from the wiki index
• Remove index entries for deleted pages
• Organize project entries and related standup links

Compare changes across Git worktrees, branches, and pull requests through a facilitated discussion between agents. Produce one consolidation plan covering the target worktree, merge order, conflicts, and decisions that need human input.

• Planning how to combine work from multiple branches
• Comparing overlapping changes and competing implementations
• Reviewing recent worktrees together

Review what Superset agents did while you were away by checking workspaces, tasks, and recent terminal output. Receive a concise digest of completed work, review requests, ongoing activity, and blockers, with the next actions listed first.

• Catching up on agent work after a break
• Finding agents waiting for review or answers
• Reviewing overnight completions and blockers

Generate brief daily check-ins, evening reflection questions, and weekly or monthly reviews for individuals and teams. Summarize supplied entries to highlight accomplishments, blockers, and supported patterns, with optional suggestions for next actions.

• Clarifying today's priorities in a morning check-in
• Drafting an asynchronous team progress update
• Reflecting on lessons at the end of the day

Interactive daily standup/meeting update generator. Use when user says 'daily', 'standup', 'scrum update', 'status update', 'what did I do yesterday', 'prepare for meeting', 'morning update', or 'team sync'. Pulls activity from GitHub, Jira, and Claude Code session history. Conducts 4-question interview (yesterday, today, blockers, discussion topics) and generates formatted Markdown update.

The English summary is being prepared. Showing the original description.

Summarizes open pull requests into a blockers-first standup digest. Activates when the user asks to summarize open PRs, find blocked pull requests, generate a PR standup, or triage review backlog from a PR export.

The English summary is being prepared. Showing the original description.

You are an expert team communication specialist focused on async-first standup practices, AI-assisted note generation from commit history, and effective remote team coordination patterns.

The English summary is being prepared. Showing the original description.

Produce a concise read-only Agiflow status summary covering completed work, work in progress, blockers, and recommended next priorities. Use for daily standups, morning checks, stakeholder updates, or a quick project pulse.

The English summary is being prepared. Showing the original description.

Generate a daily standup summary from recent Claude Code sessions — completed work grouped by project (cwd), session costs from the pricing engine, tool invocations, error/compaction/APIError events, and turn velocity metrics from session metadata (turn_count, total_turn_duration_ms).

The English summary is being prepared. Showing the original description.

Run the measurement and ceremony layer of a delivery team: the metric set, estimation and capacity, the five sprint ceremonies, and the sprint report and quarterly rollup. Use this skill whenever the user is acting as PMO or scrum lead, planning a sprint, running standup, refinement, review, or retro, measuring velocity, cycle time, or throughput, checking capacity, or reporting on how a team is doing. Triggers on PMO, sprint planning, plan the sprint, standup, refinement, backlog grooming, sprint review, retro, velocity, capacity, cycle time, lead time, throughput, WIP, burndown, carryover, sprint report, story points to hours, how is the team doing, delivery metrics, agent lanes. Also triggers when the user asks how much work fits in a sprint or whether a team is on track, even if they never say sprint or PMO.

The English summary is being prepared. Showing the original description.

A standup or status update on the user's own recent work, from the coding-agent sessions Cognee recorded (prompts, edited files, what was left open) per project. Default last 24h; also today, yesterday, 48h or a date.

The English summary is being prepared. Showing the original description.

Use at the start of a working day (or when the user asks "what should I focus on today / give me my brief / daily standup"). Produces a one-screen daily brief — today's top 3, open loops that need a nudge, what's slipping, and a suggested focus order. Trigger on "/daily", "daily brief", "what should I focus on today", "morning brief", "standup".

The English summary is being prepared. Showing the original description.

Interactive daily standup/meeting update generator. Use when user says 'daily', 'standup', 'scrum update', 'status update', 'what did I do yesterday', 'prepare for meeting', 'morning update', or 'team sync'. Pulls activity from GitHub, Jira, and Claude Code session history. Conducts 4-question interview (yesterday, today, blockers, discussion topics) and generates formatted Markdown update.

The English summary is being prepared. Showing the original description.