planning-cadence

Designs multi-layered planning cadences across annual, quarterly, and weekly horizons using sourced frameworks.

1.3k|169|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/RefoundAI/lenny-skills --skill planning-cadence
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planning-cadence
Source: https://github.com/RefoundAI/lenny-skills/tree/main/skills/planning-cadence
Command: npx skills add https://github.com/RefoundAI/lenny-skills --skill planning-cadence

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Product teams struggle to align long-term strategy with short-term execution, often ending up with rigid annual roadmaps or empty planning rituals disconnected from real strategy. This Skill helps you design a tiered planning system that matches your company stage and market volatility.

Core Features & Use Cases

  • Cadence Audit & Design: Evaluate whether your current planning frequency fits your organization size, then select frameworks like the W Framework, M Framework, or rolling six-month roadmaps.
  • Tiered Resolution Planning: Apply variable-resolution planning where the near quarter gets detailed project lists and the far quarter stays as high-level bullet points, as practiced at Notion and Figma.
  • Framework Library: Access 49 named frameworks, templates, and checklists from companies like Snowflake, Shopify, Linear, and Ramp, including Snowflake's Big Boulders and Perplexity's 75% Weekly Goals.
  • Use Case: A Head of Product at a 100-person company transitioning from ad-hoc sprints to structured quarterly planning can use this Skill to choose between the W and M frameworks and set up weekly checkpoint rituals.

Quick Start

Ask the assistant to help you design a quarterly planning process for your product team using the planning-cadence skill.

Frequently Asked Questions about planning-cadence

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose between the W and M planning frameworks?

The W Framework suits annual planning with strong top-down direction, moving between leadership and teams in four steps: context, plans, integration, and buy-in. The M Framework works for quarterly planning that starts bottom-up from product pods when no new top-down guidance exists.

How should planning cadence change as a company grows?

Pre-PMF teams under 20 people should plan in two-week sprints with no backlog. Companies around 100 people plan one to two quarters out, while 500+ person portfolios plan quarterly with bi-annual OKRs, reserving the right to discard plans when conditions change.

What is tiered or variable-resolution planning?

Variable-resolution planning details the immediate quarter with specific prioritized projects while keeping the following quarter as high-level bullet points. Notion and Figma use this approach to maintain near-term rigor while preserving flexibility to adjust future plans as strategy evolves.

How much time should teams spend on planning versus execution?

The 10% planning rule suggests spending no more than 10% of an execution period on planning, such as one week of planning for a 10-week quarter. Shreyas Doshi notes that with a pre-aligned strategy, planning can collapse from weeks to days.

When should a team avoid rigid planning processes?

Avoid heavy process for very small teams of two to three people, where continuous shipping outperforms formal sprints. Process reduces variance but can drag high performers down to average, so shield top talent from unnecessary rituals and abandon annual planning entirely during crises.