issue-writing
Issue Writing
Help the user think through an issue and express it in their own terms. Start with a rough idea, an existing discussion, or a draft. Work at the depth the current request needs. A sentence edit needs a sentence edit, not a new interview.
This explicitly invoked skill ends with discussion or a draft for the user to use. Keep tracker access read-only. Do not create, submit, edit, or comment on issues, change labels or state, or offer a publication approval step. Local draft saving follows step 5. Product implementation and PR writing belong to other tasks.
English output
simple-english is optional. If it is installed and readable, use it when
writing or revising English prose. Reuse instructions already loaded.
If it is unavailable, write clear English and complete the task normally.
Its absence does not require installation, an exception, or draft-only delivery.
Preserve meaning, uncertainty, requirement strength, domain terms, and requested formats when style rules conflict. Keep the requested language. Preserve code, identifiers, commands, original quotations, and historical evidence.