nzt-software

Plugin nzt-software from marketplace nzt in Ezefeola/nzt-ai. Commands read from the repo's manifest — 2 days ago.

Skills (12)

• architecture

  Use when how it is made has to be decided before the work - its parts and boundaries, technologies and practices, the agent's tools, the domain model, one feature's technical design, integrations, decision records, debt, diagrams.

• delegate

  Use before handing work to a subagent - a reading, or a unit the approved plan marked parallel: whether the mode allows it, the prompt, and how to check what comes back.

• design

  Use when the form of what a person perceives or operates has to be decided - layout, content, states and navigation, a mockup or prototype, the design system and voice, a usability review, the end user's manual.

• discovery

  Use when what it must do and for whom has to be agreed - purpose, rules, scope, vocabulary, specs and stories, changing what was agreed, or reconstructing it from existing work.

• learn

  Use when the user wants to acquire or improve a skill instead of having it built for them: learning, practising, being corrected, assessed, or keeping it from fading.

• nzt

  NZT's working method - the rules for every reply and where each request goes. Load it first in every session, before anything else, even for a question, and again after the conversation is compacted.

• plan

  Use when a plan has to be built, approved, changed, executed or resumed, when a feature the user accepted is closed, and whenever Plan/state.json is read or written - its schema lives here.

• research

  Use before stating or building on how an external system, API, library, standard or agent tool (an MCP server) behaves: the version in use, the authoritative source, every claim labelled.

• retro

  Use only when the user asks for a retro of a session: proposals to improve the project and NZT from where the agent stumbled, written to a file outside the repo. Changes nothing else.

• ship

  Use when the work goes to other people - version control, changelog and versions, the release pipeline, releasing, deploying or publishing, monitoring a release, rolling back.

• software

  Use for the code of a component Docs/Architecture/tech.md declares - its language, framework and practices (C#, .NET, Blazor, DDD, backend, frontend) - before designing, writing, testing or shipping it.

• verify

  Use when what was made needs evidence - test plans from a story, test data, running scenarios, exploratory sessions, performance, regression, defects - or reading the work or documents for what does not hold.

Subagents (2)

• explorer

  Read-only explorer for NZT. Use only when the nzt-delegate skill sends a reading here - surveying unfamiliar code, searching the whole repository, or researching on the web.

• worker

  Runs one approved NZT unit that the plan marked parallel. Use only when the nzt-delegate skill sends a unit here - never for reading, planning or questions.

Similar plugins