planlisted

Create or update a plan in `docs/plans/active/` from an isolated task worktree. ## Goals - Turn a request into a versioned plan that survives context loss - Define acceptance criteria and evidence before deep implementation - Make later review and verification cheaper - Keep plan artifacts out of the default checkout by ensuring a task worktree before the first file write ## Steps 1. Read `AGENTS.md`, `CLAUDE.md`, relevant `.claude/rules/`, and existing active plans. 2. Inspect only enough code and docs to understand the request and blast radius. 3. If a GitHub issue number or URL is provided: a. `gh issue view <number> --json title,body,labels,number` b. Pre-fill: Objective from title, Related request from body, Related issue: #N c. If no issue provided: set "Related issue: N/A" 4. Choose a branch type (`feat`, `fix`, `docs`, `chore`, `refactor`, `test`, `ci`, `build`, `perf`, `release`, or `security`) and a stable slug from the request. 5. **Ensure the task worktree before creating the plan file**: - First run `./scripts/ralph-worktree.sh current`. If it returns a matching task state (for example from `/spec` handoff), adopt that worktree and do not create a second one. - Otherwise run `./scripts/ralph-worktree.sh ensure --id plan-<slug> --kind standard --branch <type>/<slug> --path .claude/worktrees/<slug> --canonical-ref "<issue URL, spec reference, or request summary>" --cleanup-policy pr-success`. - The helper must create the worktree from a clea