ezefeola/nzt

Settles how a work is made once what it must do is agreed, for any work in any domain - what it is made with, how it is organised so it can be maintained, how it is checked, its conventions, third parties and delivery, and then the tools to work with all that - asking the person each choice with concrete options and writing Docs/How/how.md. Use after the define skill hands over a new planned work, when a part or unit needs a choice of how that is missing, when the person asks what it will be built or done with, or wants to change a technology, supplier or method already chosen.

Agrees what a work must achieve and for whom, in any domain (an app, a course, a book, an event, a house move, research) - interviews the person in plain language, keeps every question and answer, writes the work's definition and each part's, and turns a change to what was agreed into a proposal the person approves. Use when nzt hands off new or unclear planned work, when a part is about to be worked on and has no definition or an open question that blocks it, when the person wants to add, change or remove something already agreed, or when they ask for a spec, brief or requirements.

Does one unit of work in any domain - or guides the person through it - then verifies it against its done criterion, records it and stops with a plain report and a recommended next step. Use when nzt hands off direct work, when a planned unit or an approved batch is next, or when the person says to continue the work.

Teaches the person a skill in any domain (a spreadsheet formula, a language, cooking, an instrument, code) instead of doing the work for them - one lesson in the conversation, or a whole topic with objectives, exercises with the solution kept apart, corrections, an assessment and spaced reviews. Use when the person wants to learn, practise, be corrected or assessed, says "teach me" or "I want to learn, don't do it for me", or resumes a topic they are learning.

The nzt working method's base skill - how to talk to the person and where each request goes, for any work in any domain (software, writing, a course, research, an event, a house move, learning something). Load it first in every session, before anything else, even for a question, and again after the conversation is compacted. It reads the work's state, sizes the request, works out who does it, and routes it to the method's skill that owns it - define, approach, plan, do, learn, tools or retro.

Turns a planned or sliced piece of work, in any domain, into a plan the person approves once - units in order, the part each belongs to, what each leaves, its done criterion, who does it, and what can be cut under a fixed deadline - and records it in Plan/state.md. Use after define and approach have settled what the work is and how it is made, when the person asks for a plan, or when the units or their order have to change.

Reviews how a piece of work went, in any domain, and writes a file of improvement proposals for the work itself, for the nzt method and for domain packages, each tied to a moment where the work cost more than it should. Use only when the person asks for a retro, a review of how the work or the sessions went, or lessons learned; never offer or start it on your own. It changes nothing but its own file.

Proposes, researches, installs, checks and records the tools the agent works through (a plugin, an MCP server, a program, or a domain package) for any work in any domain, always asking the person and never adding one on its own. Use after approach settles what a work is made with, even when nothing seems missing; whenever a tool would do the work better or something is missing, before or in the middle of the work; when a domain package is to be installed; or when the person asks whether there is a plugin, MCP or tool for what they want.