Found during PR #812 review.
The shipped using-holodeck skill at pkg/skill/data/skills/using-holodeck/SKILL.md documents these workflows:
- `holodeck list` / `holodeck list -o json`
- `holodeck status `
- `holodeck ssh ` / `holodeck ssh -- nvidia-smi`
- `holodeck scp :`
- `holodeck delete ` (this one exists)
- `holodeck cleanup vpc-`
- `holodeck os list`
But on `main` today only `create`, `delete`, and `dryrun` are registered (see `cmd/cli/main.go`). AI agents installing this skill will be told to run commands that don't exist and will hallucinate.
PR #812 shipped the aspirational content per explicit Team Lead override (with a documented note that other subcommands would land in separate PRs). This issue tracks the reconciliation needed before `v0.3.0` cut:
- Option A: trim `SKILL.md` to the actual command surface on `main` (`create`, `delete`, `dryrun`) and re-grow it as commands land in separate PRs.
- Option B: implement the referenced subcommands (`list`, `status`, `ssh`, `scp`, `cleanup`, `os`) and merge them before `v0.3.0` cut.
The v0.3.0 release is in a bug-fix sprint, so Option A is the lower-risk path absent a strong reason to expand scope. Either way, this should not ship to users as-is.
Posted via Team Lead workflow after PE review of PR #812.
Found during PR #812 review.
The shipped
using-holodeckskill atpkg/skill/data/skills/using-holodeck/SKILL.mddocuments these workflows:But on `main` today only `create`, `delete`, and `dryrun` are registered (see `cmd/cli/main.go`). AI agents installing this skill will be told to run commands that don't exist and will hallucinate.
PR #812 shipped the aspirational content per explicit Team Lead override (with a documented note that other subcommands would land in separate PRs). This issue tracks the reconciliation needed before `v0.3.0` cut:
The v0.3.0 release is in a bug-fix sprint, so Option A is the lower-risk path absent a strong reason to expand scope. Either way, this should not ship to users as-is.
Posted via Team Lead workflow after PE review of PR #812.