planlisted

# Writing Plans **Speak the repository's language.** The first script this skill runs — `<cue>/gate`, or `<cue>/init-check` — prints a `language` line. **Everything you say to the user goes in that language, starting with your first sentence**: the questions you ask, not only the record you write at the end. This skill body is English because it is the plugin's source, not because it is your output. Template headings, commit markers, `outcome.md` status tokens, paths and code stay exactly as written. ## Overview Write comprehensive implementation plans assuming the engineer has zero context for our codebase and questionable taste. Document everything they need to know: which files to touch for each task, code, testing, docs they might need to check, how to test it. Give them the whole plan as bite-sized tasks. DRY. YAGNI. TDD. Frequent commits. Assume they are a skilled developer, but know almost nothing about our toolset or problem domain. Assume they don't know good test design very well. **Announce at start:** "I'm using the cue-dev:plan skill to create the implementation plan." **Context:** If working in an isolated worktree, it should have been created via the `cue-dev:using-git-worktrees` skill at execution time. ## Prerequisite check **Run this first.** It settles whether this stage may run here, against which KEY, and what is available instead if it may not. ``` <cue>/gate plan ``` `<cue>` is the scripts directory named in your session context. Substitute t