Loading...
Loading...
Found 58 Skills
(NS) Gated PM workflow — clarify, structure, RICE/WSJF, sprint plan, PERT/Monte Carlo forecast; risk, status, meeting, OKR. Also commercial budget (orçamento, Function Points, proposta comercial; COSMIC/CFP only if asked), triple productivity delivery schedule (cronograma P100/P85/P50, prazo, when we deliver), and requirements enricher / grill-me for GitLab issues or chat. Use on transcripts, backlog, timeline, delivery date, status, orçamento, cotação, cronograma, enrich requirements — even if PM is unnamed. On "help" / "exemplos", list example prompts only. Do NOT use for coding, SDD requirements generation, or GitLab issue execution.
Use this skill when designing OKR systems, writing performance reviews, running calibration sessions, creating PIPs, or building career ladders. Triggers on OKRs, performance reviews, calibration, PIPs, career ladders, leveling frameworks, feedback cycles, and any task requiring performance management system design.
The meta-framework for how a company runs -- the connective tissue between all C-suite roles. Covers operating system selection (EOS, Scaling Up, OKR-native, hybrid), accountability charts, scorecards, meeting pulse design, issue resolution (IDS), 90-day rocks, and communication cadence. Use when setting up company operations, selecting a management framework, designing meeting rhythms, building accountability systems, implementing OKRs, or when user mentions EOS, Scaling Up, operating system, L10 meetings, rocks, scorecard, accountability chart, quarterly planning, or meeting cadence.
Operations leadership for scaling companies. Process design, OKR execution, operational cadence, and scaling playbooks. Use when designing operations, setting up OKRs, building processes, scaling teams, analyzing bottlenecks, planning operational cadence, or when user mentions COO, operations, process improvement, OKRs, scaling, operational efficiency, or execution.
This skill is activated when the user's team faces execution problems—such as failing to meet OKRs, constantly changing plans, and passive team response to instructions. Typical trigger signals: Goals are set but execution deviates, plans can't keep up with changes, and the team only completes assigned tasks without proactive thinking. Non-trigger scenarios: Execution is good and only needs fine-tuning, the problem lies at the strategic level rather than the execution level, and individual work does not require a team execution framework. Difference from the "Strategy-Tactics Dialectics" skill: This skill solves "how to balance the three dimensions of execution" (execution layer), while the latter solves "dialectical design of offensive and defensive levels" (strategy layer).
Support strategy, OKR, roadmap, and prioritization work using PM Brain’s strategy frameworks.
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.
Strategic product leadership toolkit for Head of Product including OKR cascade generation, market analysis, vision setting, and team scaling. Use for strategic planning, goal alignment, competitive analysis, and organizational design.
Only for Calendar, Tasks, Approvals, Attendance, and OKR; it is not a universal entry for all Feishu office requests. This Skill must be used when users request freebusy, finding common free time, booking meeting rooms, accepting/rejecting invitations, creating or replying to schedules, managing tasks/checklists, initiating, withdrawing, approving, rejecting, transferring, or cc'ing approvals, checking clock-in/lateness/leave statistics, querying OKR cycles, or updating progress. It is explicitly prohibited for use in user/department address books, emails, historical meeting retrieval, meeting recording, or Minutes; these use feishu-cli-platform, feishu-cli-mail, and feishu-cli-meetings respectively. Meeting notification messages use feishu-cli-messaging.
Writes effective OKRs using Christina Wodtke's best practices and Google's OKR methodology. Use when setting goals, aligning teams, creating measurement frameworks, or tracking quarterly progress.
Set aligned, measurable OKRs/goals and produce an OKR & Goals Pack (objectives, key results, anti-gaming guardrails, systems/habits, review cadence, grading plan).
Drafts, reviews, rewrites, and coaches outcome-based OKR sets across team, department, product, or company scopes. Supports five entry modes (Guided default, One-Shot via --oneshot, Sustained Coach, Audit Only, Rewrite). Diagnoses empowered-team context and adjusts framing; refuses to fabricate baselines or targets; refuses to use OKR scores for compensation; reframes feature-delivery KRs into outcome KRs. Use when planning quarterly OKRs, translating strategy into team outcomes, reviewing draft OKRs for quality, or converting roadmap-as-OKR drafts into proper OKR sets.