Loading...
Loading...
Found 19 Skills
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) 🇨🇳 Your team has high autonomy — but standups are getting vague, weekly meetings turn into status reports, and you can't get honest answers in 1:1s. This three-layer Motivation playbook solves exactly this problem: standups are the information layer, weekly meetings are the alignment layer, and 1:1s are the individual layer. When these three things are done right, motivation isn't managed—it grows naturally. 🇯🇵 Your team has high autonomy, yet standups are vague, weekly meetings turn into progress reports, and you only get "I'm fine" in 1on1s — this playbook solves all three layers at once. 🇰🇷 Your team has high autonomy, but standups are vague, weekly meetings turn into progress reports, and you can't get honest feedback in 1:1s — this playbook solves all three layers simultaneously. Triggers: "team motivation" | "no one writes standups" | "weekly meetings turn into status reports" | "can't get honest answers in 1:1s" | "high-autonomy team management" | "how COOs manage teams" | "team motivation" | "standup best practices" | "1on1 framework" | "weekly meeting template" | "team motivation" | "team motivation" | "AI startup team ops" | "remote team alignment" | "engagement decline"
Generate a stakeholder update tailored to audience and cadence. Use when writing a weekly or monthly status for leadership, announcing a launch, escalating a risk or blocker, or translating the same progress into exec-brief, engineering-detail, or customer-facing versions.
Read-only exploration, status checks, and reporting without modifications. Use when user asks to check status, find files, search code, show state, or explicitly requests read-only investigation. Do NOT use when user wants changes, fixes, refactoring, or any write operation.
Maintain project state across MULTIPLE conversations over days/weeks. Track tasks, decisions, blockers, resources. Auto-update when project mentioned. Generate status reports and proactive reminders.
Manage stakeholder expectations and engagement through targeted communication, regular updates, and relationship building. Tailor messaging for different stakeholder groups and priorities.
Draft stakeholder updates tailored to audience — executives, engineering, customers, or cross-functional partners. Use when writing weekly status updates, monthly reports, launch announcements, risk communications, or decision documentation.
Compose professional internal communications using company-preferred formats. Covers 3P updates, newsletters, status reports, leadership updates, project updates, and incident reports.
Write internal communications using company formats. Use when writing status reports, leadership updates, company newsletters, FAQs, incident reports, project updates, or any internal communications.
Plan and track projects with timelines, resources, and risk management
Master stakeholder communication with presentations, status updates, expectation management, and effective collaboration techniques for product success.
Write internal company communications — 3P updates (Progress/Plans/Problems), company-wide newsletters, FAQ roundups, incident reports, leadership updates, status reports, project updates, and general internal comms. Use this skill any time the user asks to draft, edit, or format something meant for internal audiences. Trigger on keywords like "3P", "weekly update", "newsletter", "FAQ", "internal comms", "status report", "company update", "team update", "incident report", or any request to summarize work for leadership, teammates, or the broader company. Even casual requests like "write my update" or "summarize what my team did this week" should trigger this skill.
Use when the war plan is approved and it is time for parallel execution — dispatches soldiers through capos to implement work packages with TDD enforcement, tribute collection, and escalation protocols