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.

Writes an actionable markdown implementation plan with bite-sized TDD tasks, exact paths, code, and commands, without executing it.

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

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

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.

Create detailed phase plan (PLAN.md) with verification loop

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

Reviews a plan from a prior session by extracting the canonical reference prompt from seed/plan-reviewer-design.md and invoking the plan-reviewer agent with it, surfacing the verdict without auto-applying changes.

Plan mode for Hermes — inspect context, write a markdown plan into the active workspace's `.hermes/plans/` directory, and do not execute the work.

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

Creates and maintains persistent markdown planning files that survive session resets by hooking into Claude Code's lifecycle.

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

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

Chrome-dependent academic literature scouting and idea planning. Use when the user gives a research idea, topic, question, or draft direction and wants Codex to browse Google, Google Scholar, and academic sources through the Codex Chrome plugin, identify relevant papers, explain what can be borrowed from them, and write a planNN.md before collecting PDFs or BibTeX.

Decompose multi-step work into a revisable subgoal plan with stable step IDs, checkpointing, and plan-ahead execution. Load when a task needs explicit planning before action, subgoal decomposition, plan checkpointing, or ReCAP-style plan-ahead execution. Also triggers on "structured plan", "plan with steps", "subgoal graph", "revise the plan", "checkpoint plan", or multi-step tasks where naive one-shot execution would be fragile. Skips trivial single-step tasks. Pairs with dynamic-routing on failure. Distinct from process-decomposer (registry/triage) and problem-to-plan (doc deliverables).

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.

Breaks a PRD into a multi-phase implementation plan using tracer-bullet vertical slices, saved as a local Markdown file in ./plans/.

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.

Opens plans and HTML artifacts in a local browser canvas where the human annotates elements, chats, and approves or requests changes without leaving the page. Use when presenting a plan for review, or when feedback like "move this, change that" is easier pointed at than typed.

Plan a feature from BRD-lite brief or clear intent into PRD (What), decisions, implementation plan, and task slices.

Create and manage persistent markdown planning files for structured task execution. Use when the user asks to "create a plan", "track progress", "start a research project", or when a task requires more than 5 tool calls and needs structured phase tracking to stay focused and avoid goal drift.

Use this skill whenever a developer wants to turn an idea into a complete, production-ready, end-to-end system plan BEFORE writing any code. Trigger on 'plan this system', 'design the architecture for', 'help me blueprint', 'deep plan for X', 'break this idea into components', 'expand into action points', 'full implementation plan', or when the user pastes a project idea wanting architecture, components, pipelines, and file-level execution mapped out. Casual phrasing also triggers: 'help me think this through end-to-end', 'plan before coding'. Also covers living-workspace patterns: self-improving knowledge bases, reflection loops with auditor agents, four-agent teams, schema-as-code, wiki health scoring. **Resume triggers**: 'where did we leave off', 'continue this plan', 'resume my blueprint' - rehydrates state from disk via SESSION.md/NEXT.md/decisions/. Web research is mandatory every invocation.

Structured task planning with clear breakdowns, dependencies, and verification criteria. Use when implementing features, refactoring, or any multi-step work.

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

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

Diagnoses and tunes PostgreSQL performance issues such as slow queries, missing indexes, bloat, locks, and connection problems, providing SQL commands and best practices.