Results for “planka”

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.

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".

Opens a conversational planning session for a feature, bug, or ticket. Investigates the repo, discusses the approach with the user until a solution is agreed, and only then writes the plan to docs/plans/. Use whenever the user invokes it, describes a problem to solve, pastes a ticket, mentions an incident, or asks to plan a non-trivial change. Also on "plan this", "analyze this first", "what would we need to touch", "let's start with this" — or in Spanish "planeá", "analizá esto antes", "qué habría que tocar", "arranquemos con esto".

A relentless interview to sharpen a plan or design.

Reads a plan document, decomposes it into steps, designs a per-step agent chain from the ECC catalogue, and emits ready-to-paste /orchestrate custom prompts without executing them.

For custom ZK Solana programs and privacy-preserving applications to prevent double spending. Guide to integrate rent-free nullifier PDAs for double-spend prevention.

Use when implementing elk functionality with production-grade patterns and safeguards.

Runs a relentless interview that sharpens a plan or design. Use when the user wants to be grilled on an idea, pressure-test a plan, or refine a design through questioning.

Build a personalized study plan with spaced-repetition scheduling toward a deadline and goal.

Generate Minervini-style breakout trade plans from VCP screener output with risk calculation, portfolio heat management, and Alpaca-compatible order templates.

Shape or refine the existing bead or caller intent without creating a second planning artifact. Triggers: "plan", "discover and plan", "shape this goal".

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

Select alternative execution paths when a plan step fails — branch on outcomes instead of blind retry. Load when a structured plan step fails, an unexpected observation arrives, or the user asks what to try next after an error. Also triggers on "try another approach", "route around this failure", "replan on failure", "if X fails try Y", or outcome-based branching during multi-step work. Pairs with structured-planning and debug-and-fix. Does not replace root-cause debugging — adds plan-level path selection.

御坂美琴（少年漫）认知与表达框架（压缩蒸馏）：炮姐傲娇、正义感、学园都市梗 触发：某科学的超电磁炮 等。虚构

Plan gala events with programming and fundraising. TRIGGERS - Use when user needs help with gala-plan related tasks.

Detect monorepo structure, identify shared chokepoints, and generate safe parallel lane specs aligned to package boundaries

Creates executable Polars dataframe contracts using Pandera's Polars backend for runtime validation of schemas, columns, and checks.

Plan gala events with programming and fundraising. TRIGGERS - Use when user needs help with gala-plan related tasks.

Compare, cross-review, and merge competing plans from multiple agents into one executable direction with a clear handoff.

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

PUA Pro extensions: self-evolution notes, compaction state continuity, KPI-style summaries, flavor switching, and feedback tools.

Run a Virtual Think Tank — a structured multi-persona debate — before planning or making architectural/design/strategic decisions. Use this skill whenever the user is about to plan a system, make a technology choice, evaluate trade-offs, decide on an approach, or faces any decision where multiple perspectives would sharpen the outcome. Also trigger when the user says "think tank", "debate this", "perspectives on", "trade-offs", "should I use X or Y", "help me decide", "before we plan", or asks for pros/cons of competing approaches. This skill should run BEFORE any implementation planning begins — it produces a structured analysis that feeds into better plans.