do-issuelisted

# Create Issue (Quality Issue Creator) Create a GitHub issue that is a self-contained document a stranger could understand. Every issue must teach the reader what they need to know — define terms, link sources, and state the problem from the reader's perspective. The `/do-plan` skill reads the issue as its primary input: quality here directly determines plan quality downstream. ## Repo Context Probe If `.claude/skill-context/do-issue.md` exists, read it and honor its declarations; otherwise use the generic defaults described below. The context file is where a repo layers its SDLC automation onto this generic baseline: a stage/status marker to write at the start and end, cross-repo `gh` targeting, the canonical doc locations to search for related context, and the plan-doc path convention the issue should reference downstream. When the file is absent (the common case in a foreign repo), this skill runs entirely on `git` and `gh` — no repo-specific tooling required. ## Core Philosophy: Think Like a Teacher The reader of your issue has general software engineering experience but **zero context about this specific codebase**. Every named concept that isn't common knowledge needs: 1. A one-sentence definition 2. A link to its source (repo, docs page, file path, or RFC) This isn't optional politeness — it's functional. Undefined terms produce vague plans. Defined terms produce precise plans. ## When to load sub-files | Sub-file | Load when... | |----------|-------------| |