Brainstorm a feature or change with the user, explore the repo to understand how it fits, then produce a concrete implementation plan. Creates a plan in `~/.k/workspaces/...`.
${CLAUDE_SKILL_DIR} may point at this directory. In Codex-style environments, resolve sibling paths like assets/plan-template.md directly from this SKILL.md.CLAUDE.md, AGENTS.md, README, or repo-specific contributor docs.!echo ~/.k/workspaces/${PWD////_}`` — all plan and follow-up files live here. Create subdirectories as needed.<feature_description> $ARGUMENTS </feature_description>; if it is empty, ask what they want to plan and stop.!echo ~/.k/workspaces/${PWD////_}/plans/YYYY-MM-DD-NNN-slug.md where YYYY-MM-DD is today's date, NNN is the next available zero-padded sequence for that date, and the slug is a short kebab-case summary (3-5 words). Create the directory if it does not exist.assets/plan-template.md.
Related code must be concrete: repo-relative paths plus one-line reasons each file matters. Vague references like "the auth module" are not useful.assets/architecture-review-prompt.md, then compose the actual review prompt with the concrete plan path, repo guidance docs, and the most relevant files or modules from Related code./kwork in a fresh session or with cleared context if the host environment supports that. Planning conversations consume significant context, and a fresh implementation session preserves room for the actual coding work.