Results for “capability-plan”

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.

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.

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.

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

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

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.

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

Plan soak test planner operations. Auto-activating skill for Performance Testing. Triggers on: soak test planner, soak test planner Part of the Performance Testing skill category. Use when writing or running tests. Trigger with phrases like "soak test planner", "soak planner", "soak".

Eng manager-mode plan review. (gstack)

List Available Fabric Capacities

通用规划抽象接口。当定义规划过程、策略制定、目标分解时调用此技能。

Creates executable implementation plans that break down a brainstorming design into detailed, unambiguous per-batch tasks for execution.

Design APQP plans for product quality. TRIGGERS - Use when user needs help with apqp-plan related tasks.

Turn a rough idea into a fully approved design before any code is written. Load when the user wants to brainstorm, explore ideas, design a feature, think through approaches, plan a new capability, or figure out what to build. Also triggers on "let's think through", "help me design", "explore options", "what's the best approach for", "I have an idea for", "before we build", or any request to design something before implementation. Enforces a hard gate: no code, no implementation until user approves a design. For executable feature specs (FRs, NFRs, ACs as Given/When/Then), route to `feature-spec` instead — brainstorming owns approach and architecture, not machine-readable requirements.