Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
Design & UI

plan

Helps the user design a lab workflow by asking questions, working through steps together, and writing the result to a plan.md file. Use when planning a new lab run, benchmarking test, or database experiment.

rustyrazorblade · Static checks on file

Installation

Read the source and dependencies before running a command. Copying does not install or execute anything.

npx skills add rustyrazorblade/skills --skill plan

About this skill


name: plan description: Helps the user design a lab workflow by asking questions, working through steps together, and writing the result to a plan.md file. Use when planning a new lab run, benchmarking test, or database experiment. argument-hint: "[what you want to accomplish] [--binary ] [--output ] [--previous ] [--interactive]" user-invocable: true

Easy DB Lab — Plan

You are helping the user design a lab workflow. Your job is to ask the right questions, help them think through the steps, and produce a clear plan.md they can follow.

Environment

Load ../../references/environment.md for details on the AWS environment, k3s, observability stack, Cassandra config patches, and SSH access.

Previous Run (optional)

If --previous <cluster-dir> was provided, read the following files before asking any planning questions:

  • <cluster-dir>/docs/journal.md — what was done, what was observed, what worked and what didn't
  • <cluster-dir>/docs/issues.md — friction, undocumented behavior, or gaps discovered during the run

Use these to inform the new plan: incorporate steps that were added ad-hoc, avoid approaches that failed, and address known issues. Load ../../references/journal.md and ../../references/issues.md for the format these files follow.

Discover Before You Plan

Before asking the user anything, resolve the binary, read the task-oriented guides, and run the discovery commands.

Resolve the binary — in priority order:

  1. If --binary <path> was passed as an argument to this skill, use that path as $EDB
  2. If bin/easy-db-lab exists in the current directory, use bin/easy-db-lab as $EDB
  3. Otherwise use easy-db-lab as $EDB

Use $EDB for all binary invocations in this skill.

Read the task-oriented guides first

Before the flag-level reference, read how the tool is meant to be used. $EDB help lists task-oriented topic guides; $EDB help <topic> prints one. Each guide gives the intended workflow for a topic as an ordered command sequence, plus the prerequisites and gotchas behind it — the "how the project is meant to be used" layer that commands and --help do not carry.

# List the available topic guides (provisioning, stress-testing, kits, cassandra, ...)
$EDB help

# Read the guide for each topic the plan will touch
$EDB help <topic>

Read help <topic> for every topic the plan involves before you design its steps. A guide's command sequence and its prerequisites (for example, "db nodes need a data disk: use an NVMe instance type or attach EBS") are exactly the constraints a plan must respect. Treat the guide as the intended shape of the workflow; use commands and --help below to pin the exact flags for each step.

If $EDB help errors with Unmatched argument at index 0: 'help', the binary predates the topic guides. Skip this step and rely on commands and --help below; the guides add context but are not required to plan.

The flag-level reference

# Authoritative flag and subcommand reference
$EDB commands

# All installable software available in this environment
$EDB kit list

Use commands output as the authoritative source for flag names and subcommands — never guess flags.

Use kit list output as the authoritative list of installable software. Any database, tool, or app the plan needs to install must appear in this list. If the user asks for something not in the list, stop and ask them what they mean — do not guess, do not try alternatives, and never use docker.

If the binary cannot be found, load ../../references/commands.md as a fallback and warn the user to verify flags when running the plan.

commands is the index, not the documentation — run --help per command

$EDB commands prints only a one-line description per subcommand. It silently drops the full help text, which is where the critical warnings live. Treat it as a table of contents for finding what exists, then read the actual entry.

Once you know which commands the plan will use, run --help on each one before writing any step that invokes it:

$EDB <subcommand path> --help

This is not optional and it is not redundant with commands. A worked example of the difference: commands renders cassandra profiling start as the single line "Enable continuous profiling on Cassandra nodes." Its --help additionally documents which async-profiler arguments the tool reserves and rejects, and carries a multi-paragraph warning that combining a CPU event with wall-clock sampling in one recording silently corrupts the resulting profile by up to three orders of magnitude. A plan written from commands alone can therefore contain a command that runs cleanly, produces plausible output, and is wrong — with the warning against it sitting unread in help the whole time.

Read --help for every command the plan will invoke, including ones you are confident about. Confidence is exactly the state in which a --name gets written where a positional belongs.

--help only works one level deep, and fails silently below that. easy-db-lab init --help works. easy-db-lab cassandra use --help prints the root help and exits 0 — it looks like it worked, and a session that does not notice will believe it complied with this section while learning nothing. easy-db-lab cassandra help use is not a fix either: picocli consumes help as the required <version> positional and prints the usage block as a parse error, which happens to be readable for commands with a required positional and unavailable for every other one.

So for any subcommand below the first level — everything under cassandra, cassandra stress, cassandra profile, kit, logs, metrics, spark — easy-db-lab commands is the authoritative source, and easy-db-lab <group> --help gives the group's subcommand list. Capture commands once during discovery and read the entry rather than trusting a `--he

Read the complete source ↗