Results for “planning”

Strategic planning with optional interview workflow

Design meeting rhythms, metric reporting, quarterly planning, and decision-making velocity for scaling companies.

Breaks complex problems into iterative reasoning steps with revision, branching, and dynamic scope adjustment for multi-stage analysis and planning.

Strategic planning with optional interview workflow

Manage issues, projects, and team workflows in Linear with structured workflows for sprint planning, bug triage, and release management.

Guides multi-step tasks by decomposing them into checkpoints, verifying results with concrete observations, and re-planning after surprises or failures.

Coordinates sprint planning, delivery tracking, experiment management, knowledge management, and changelog governance across project management workflows.

Creates actionable work plans through interactive interviews, direct planning, consensus loops, or plan review, with quality gates and optional multi-agent deliberation.

Decompose work into small, verifiable tasks with explicit acceptance criteria, ordered by dependencies and sliced vertically for reliable implementation.

Fetches real-time London transit data from the TfL API, including Tube and bus arrivals, line status, disruptions, journey planning, and route information.

Diagnose planning directory health and optionally repair issues

Bootstrap and run a multi-agent AI development team with parallel chats for planning, development, QA, and DevOps.

Gather phase context through adaptive questioning before planning

Structures immediate next steps into a dependency-ordered plan, gated by the current action_gate mode, with checkpoints and risk flags before execution.

Create implementation-ready engineering plans for WelineFramework. Use in Plan mode, or when the user requests detailed requirements, code modification points, task cards, test cases, acceptance criteria, risk and rollback design, or a handoff package for execution-oriented AI agents.

Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.

Calendar management and scheduling. Create events, manage meetings, and sync across calendar providers.

Generates a step-by-step construction plan from a one-line objective, where each step is self-contained and executable by a fresh agent in a new session.

Use before any complex or ambiguous task where the path forward is unclear. For breaking down multi-step problems, choosing between approaches, clarifying vague requirements, identifying hidden assumptions, planning before building, and preventing costly mistakes from starting in the wrong direction. Activate when user says "how should I approach this", "what's the best way to", "I'm not sure how to", or presents a problem without a clear solution.

Use when a user asks for a plan for a coding task, to generate a clear, actionable, and atomic checklist.

Analyze codebase with parallel mapper agents to produce .planning/codebase/ documents

Use when a user asks for a plan for a coding task, to generate a clear, actionable, and atomic checklist.

Writes an actionable markdown implementation plan to .hermes/plans/ without executing code, using bite-sized tasks, exact paths, and complete code examples.

Surface Claude's assumptions about a phase approach before planning

Executes small ad-hoc tasks with GSD guarantees, spawning planner and executor agents, tracking tasks in .planning/quick/, and updating STATE.md. Supports composable flags for discussion, research, plan-checking, and verification.

Provides a suite of five product team skills covering OKR alignment, feature prioritization, sprint planning, user research, and design systems, with scripts and templates for each role.

Execute the implementation planning workflow using the plan template to generate design artifacts.

Use when planning a STOC (ACM Symposium on Theory of Computing) project calendar — backward planning to the early-November deadline, the STOC/FOCS alternating two-deadline year that theory groups schedule around, full-version and camera-ready milestones, and the June TheoryFest endpoint.

Use when planning an ACL project calendar across ACL Rolling Review cycles, covering cycle selection against conference commitment windows, backward planning from an ARR deadline, the review-response-meta-review timeline, commitment decisions, resubmission loops to later cycles, and camera-ready through ACL Anthology publication.

Use when planning a VLDB project on the PVLDB rolling calendar, covering month-picking strategy, the volume-to-conference mapping and acceptance cutoff, budgeting a possible three-month revision, coordinating author caps across a group, and backward planning from the 25th-abstract / 1st-paper rhythm.