kinwisenz-devops/ai-kiwiniser

Use when a request is vague, when someone wants to give an agent instructions but is not sure how to word them, or when a prompt needs tightening without changing its intent. Turns a person's rough request into a clear brief an AI agent can act on: the goal in their words, the context, constraints, what done looks like and what to leave alone, asking at most one question when the answer would change the work. Do not use to do the task itself, or to explain an agent's output (plain-english-report).

Use when someone asks what code, an error, a diff or an agent's report means, when agent output needs rewriting in everyday words, or when a request must be turned into agent instructions. Router and shared house style for turning coding and agent output into plain New Zealand English that a non-expert can follow, and rough human requests into clear briefs for an agent. Do not use for writing or changing the code itself.

Use when someone asks what this code, error, change or command means, or asks for it in simple words. Explains code, diffs, error messages, stack traces, logs, config and commands in plain New Zealand English for a reader with no coding background: what it does, why it matters, what could go wrong, and the next step. Do not use for changing the code, or for summarising an agent's own report (plain-english-report).

Use when writing or checking text for New Zealand readers, simplifying wording, or deciding how to write a date, an amount or a Māori word. Applies plain-language writing and New Zealand English conventions to text: everyday word choice, short sentences, spelling, dates, numbers, currency, te reo Māori words and macrons, and acronym handling. Do not use to explain code (explain- code) or to change the meaning of the text.

Use when asked to write, rewrite or review a README, guide, how-to, tutorial, reference page or explanation. Writes software documentation in plain New Zealand English that a bright 16-year-old can follow: it picks the right form (tutorial, how-to, reference or explanation), fixes the audience, goal and scope, agrees an outline, then writes and checks every claim against the real code. Do not use to explain a single piece of code in chat (explain-code) or to change the code.

Use when agent output is too technical, too long or hard to act on, or when a close-out, summary or handover is needed. Turns an agent's plan, results, test run, status, commit message or pull request description into a short plain New Zealand English report: what happened, what it means, what the reader must decide, and what was not checked. Do not use to explain a piece of code (explain-code) or to write instructions for an agent (agent-brief).