Results for “capability-plan”

Splits a body of context into a sequence of vertical-slice build phases where each phase is independently demonstrable to a real user and each builds on the previous. Use when the user wants to plan, sequence, phase, slice, break down, or order the build of a feature, capability, system, or initiative, and produces a plain-language phased build outline. Does not produce implementation detail — use plan-implementation. Does not specify behavior that has not been decided — use plan-a-feature. Does not perform gap analysis between two artifacts — use gap-analysis. Does not break a plan into independently-grabbable work items — use plan-work-items.

Use when forecasting resource needs, evaluating if current capacity is sufficient for planned work, or sizing systems for expected load. This skill provides procedures for estimating, planning, and monitoring capacity to prevent resource shortages.

Capacity Planning — Real-Time Agent Workload Tracking

Performance-coaching mode for repeated failures, passive behavior, completion-quality issues, or explicit try-harder requests. Uses structured troubleshooting and evidence-first delivery habits.

Plan a sprint by estimating team capacity, selecting and sequencing stories, and identifying risks.

Agent skill for planner - invoke with $agent-planner

Maps support capabilities, plans cross-training, and sizes multi-skilling against real proficiency and routing cost.

Create a delivery plan with goals, capacity, scope, risks, and commitments.

Plan a sprint with capacity estimation, story selection, dependency mapping, and risk identification. Use when preparing for sprint planning, estimating team capacity, selecting stories, or balancing sprint scope against velocity.

Guides CAPA effectiveness assessment with verification methods, SMART criteria, and closure requirements.

Continues deep iteration on an existing planning document: detects explicit file-loading intent, provides status summaries, and supports on-demand in-depth exploration.

Performance-coaching mode for repeated failures, passive behavior, completion-quality issues, or explicit try-harder requests. Uses structured troubleshooting and evidence-first delivery habits.

Map career development paths with skill gap analysis and learning recommendations

Turn "can we even hit this number" into a capacity model that shows the truth before the quarter does. Models ramped-rep productivity, builds the hiring plan the target requires, states the ramp assumptions plainly, and names the gap between plan and capacity so nobody discovers it in month three. Built for B2B sales and RevOps leaders, customizable to your ramp and your CRM. Trigger on "build a capacity model", "how many reps to hit the number", "what's the hiring plan", "are we capacity constrained", "model the ramp", or any capacity or headcount planning question.

Turn "what's the plan" into a GTM plan you can defend, verdict-first. Names the two or three bets, the motions behind each, the targets, the capacity math that says whether the number is reachable, and the risks that would break it. Built for B2B GTM leaders, customizable to your model and stage. Trigger on "build our GTM plan", "plan the quarter", "is this number reachable", "what are our bets", "annual GTM planning", "do we have the capacity", or any planning cycle.

CC-Panes bundled skill: Spec 工作流

Generate structured, machine-readable implementation plans for features, refactoring, upgrades, or infrastructure changes.

Configures GKE workload reliability with PodDisruptionBudgets, health probes, topology spread constraints, and graceful shutdown patterns.

Turn a new rep's start date into a ramp that ends in quota, not confusion. Builds a 30/60/90 onboarding plan with milestones at each gate, a certification bar they have to clear before they carry full load, and the manager touchpoints that catch a slow ramp early. Built for B2B sales managers and enablement, customizable to your role and motion. Trigger on "build an onboarding plan", "30/60/90 for a new AE", "how do I ramp this rep", "certification checklist", "onboarding milestones", or any new-hire ramp.

[EXPLICIT INVOCATION ONLY] Creates dependency-aware implementation plans optimized for parallel multi-agent execution.

Build a compact, validation-gated implementation plan for multi-step, risky, or ambiguous work — typically when phases need explicit checkpoints, the change touches multiple files/services, or the user wants alignment before execution. Output goes to `.claude/plans/<topic>.md` (or `.agents/plans/`) with goal, in/out-of-scope, phased steps, validation per phase, and replanning triggers. Skip for trivial single-file fixes, bug investigations (use `tracer`), or open-ended exploration (use `explore`). Pair with `ship` once the plan ends and merge work begins.

Use this when the team needs to define permissions, roles, membership rules, resource ownership, or action-level authorization separate from authentication choice. Trigger on requests about access models, RBAC, ABAC, tenancy, or protected operations.

Use when you have a written implementation plan to execute in a separate session with review checkpoints

Agent skill for goal-planner - invoke with $agent-goal-planner

Tactical fast path: turn a small problem, bug report, edit request, or narrow refactor into three deliverables — a brief change-spec (docs/specs/), a detailed implementation-ready plan (docs/plans/), and a TODO.md with agent-pickable tasks and milestones. Load when the user describes a tactical problem and wants quick planning artifacts, says "plan this change", "create a TODO", "write a plan for this", "problem to plan", "break this into tasks for agents", "I want to change X — plan it", or when process-decomposer routes here after determining the user needs lightweight planning deliverables. Also triggers on "create tasks from this problem", "make this actionable", or "turn this into a plan agents can execute". For feature-sized work that needs an executable spec + constitution + cross-check gate, route to `spec-driven-development` (or `feature-spec`) instead.

Guides a structured planning pipeline for coding tasks, from scoping and research to plan creation, review, and handoff.

Create concise, actionable plans for coding tasks. Scope work, identify dependencies, and deliver atomic, ordered steps from discovery through validation and rollout.

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

Turns a mature product plan into a rough implementation plan with high-level steps, maturity and verification marks, and a risks section.

Structured planning methodology with research, brainstorming, phased plan creation, risk assessment, and plan-to-build continuity.

Use when a research implementation plan exists in docs/superpapers/plans/ and the user is ready to execute it — collecting data, running analysis, producing outputs, writing the paper. Orchestrates task execution with replication-driven verification and two-stage review at phase boundaries.

Guides a structured planning pipeline for coding tasks, including scope detection, research, plan creation, and review.

Plans a sprint with capacity estimation, story selection, dependency mapping, and risk identification. Use when preparing for sprint planning, estimating team capacity, or balancing scope against velocity. Triggers on: sprint planning, sprint plan, capacity planning, sprint scope, story points, sprint goal, backlog grooming, sprint prep, what do we build this sprint.