Issue

Interpret MUST, MUST NOT, SHOULD, SHOULD NOT, MAY, etc. per RFC 2119.

The user MAY provide a title as an argument (e.g. /chalk:issue flaky expression_test under load). If no title is provided, draft one from the conversation.

This skill owns the issue description — drafting it, creating the issue, and keeping the description accurate later. It does not track a session against the issue: "open an issue for this so we don't lose it" is this skill on its own. Filing and picking it up is chalk new, which runs this skill to produce the issue and then starts tracking.

Before you draft

An issue description is an explanation artefact, and it MUST be drafted against the chalk voice. Load these first (via the Skill tool):

• chalk:voice, and its references/palette.md — the principles, the section palette, the line-format rule.
• chalk:mindmap — the shape of the content inside each section.
• chalk:goal-tree — wherever a section's children accomplish their parent rather than argue for it.