taskmaster-issueslisted

# Writing a Task Master issue Only relevant to a project where Mullion's Task Master is enabled — if this repo doesn't have a background task watcher polling its issues, this skill doesn't apply. See `docs/tasks.md` for the full system; this is just the "how do I write the issue" cheat sheet. ## What the worker actually gets Before anything else: your issue's **title and body are passed to the worker verbatim** — title, a blank line, then the body, nothing stripped, not even the directive lines below. There is no parsing, no summarization, no expansion: whatever isn't in the text you write is invisible to the agent that implements it. - **No parent issue, epic, or linked issue is ever pulled into the prompt.** A bare `#123` reference is just four characters to the worker — it never resolves to that issue's content. - **The same title+body is what the reviewer judges the diff against**, when a review agent is configured — your body is the acceptance spec, not a hint. - Mullion's own preamble already covers running the repo's verification gate, self-reviewing the diff before committing, and leaving the worktree clean. Don't repeat any of that in your Scope. ## The label Task Master's watcher polls each connected project's repo for open issues carrying a specific label — `mullion-task` by default. **No label, no pickup** — an issue without it just sits there, however well-formatted the body is. The label is a deploy-time setting, not something a project or an i