submit-issuelisted

# Submit Issue Skill Open a GitHub issue for the prospec repo in the house format. The format below is derived from the merged issue corpus (#179–#196, #203–#208); this skill executes the pattern, and newer merged issues outrank it when they disagree. ## Language The issue **body is Traditional Chinese (Taiwan)** — a house convention, same rationale as PR bodies: the Constitution's `[MUST] Language Policy` is defined over repo *paths*, and an issue body is not one (see `prospec/CONSTITUTION.md` → Language Policy, mirrored in `CLAUDE.md`). The **title stays English** in conventional-commit form, as do code identifiers, file paths, and technical terms inside the body. **Never append an AI attribution footer.** The repo uses **no labels** — do not add any. ## Scope discipline — one issue per change Size each issue so it maps to exactly **one prospec change / one PR** (`/prospec-new-story` registers it via `prospec change story --issue "#NN"`). A body that needs two unrelated 方案 groups or two independent AC sets is two issues — split them and cross-link the series. Defects discovered mid-flight go to a change artifact or a new issue, never into frozen planning docs. ## Preconditions 1. **`gh` is authenticated as an account with write access.** With more than one account logged in, the active one can silently be the wrong one, and `gh` then fails with a *misleading* error: ```bash gh api user -q .login # must be able to write to