planlet-planlisted
Install: claude install-skill vipentti/planlet
# Planlet Plan
Create or revise one focused planlet while keeping planning separate from implementation.
## Start the workflow
1. Discover the repository root without traversing above its boundary.
2. Use one available `planlet` executable throughout the workflow. Confirm each needed operation with `planlet help <command>`; do not infer support from this skill. Pass `--root "<repository-root>"` to every operational command. Treat angle-bracket runtime values as separate argv values; when invoking through a shell, apply shell-specific escaping instead of interpolating raw text.
3. Use `planlet --root "<repository-root>" list` to inspect active logical slugs and `planlet --root "<repository-root>" list --completed` to inspect completed logical slugs. For a revision, resolve exactly one active slug, run `planlet --root "<repository-root>" validate <slug>`, and read both files completely with `planlet --root "<repository-root>" --full show <slug> --part plan` and `planlet --root "<repository-root>" --full show <slug> --part tasks`.
4. Read applicable repository instructions when present.
5. The `planlet` CLI is required. If no executable is available, install it
(`npm install -g @vipentti/planlet`) or invoke it through `npx @vipentti/planlet`. If it still
cannot run, stop and report that, naming the missing executable. Do not reimplement CLI
operations by editing planlet files.
## Develop the proposal
1. Inspect the repository before recommending an approach.
2. Loo