← ClaudeAtlas

planlet-implementlisted

Implement and verify exactly one active repository-local Planlet while updating its task checklist incrementally. Use when a user asks to execute a persisted planlet, continue its implementation, or report and advance its remaining work without archiving it.
vipentti/planlet · ★ 1 · Data & Documents · score 71
Install: claude install-skill vipentti/planlet
# Planlet Implement Implement one persisted planlet and keep its progress truthful. ## Start the workflow 1. Discover the repository root without traversing above its boundary. 2. Use one available `planlet` executable throughout. Confirm needed operations with `planlet help <command>` and 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. Resolve exactly one active planlet with `planlet --root "<repository-root>" list`. Accept one valid explicit active slug. With no slug, select and announce sole active planlet; report none; or ask user to choose when several exist. Never select by recency or output order. 4. Run `planlet --root "<repository-root>" validate <slug>`. Stop on non-zero exit. 5. Re-read both files completely with `planlet --root "<repository-root>" --full show <slug> --part plan` and `planlet --root "<repository-root>" --full show <slug> --part tasks`; use `planlet --root "<repository-root>" tasks <slug>` and `planlet --root "<repository-root>" status <slug>` for canonical progress. When the harness exposes a dedicated file-reading capability, also read each file with it before editing that file directly, because such a harness can reject an edit to a file it has not read and may not count a shell read. Treat `plan.md` as the authoritative change-specific design and acceptance contract for