Skip to content
Agentmart
Submit a tool

zno-change

Use when the user writes /zno-change or asks to change existing behavior or scope in an ongoing project.

Skill by 1447751897

IndexedMIT★ 2
Write a review

Chalk Labs

Need help deploying zno-change?

Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.

Book a call

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/1447751897-zno-change

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Use when the user writes /zno-change or asks to change existing behavior or scope in an ongoing project. Identifies the affected docs and code before implementing, updates them together with the change, and records the change in the feature changelog.

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/zno-change

What's inside

Skill name
zno-change
Description
Use when the user writes /zno-change or asks to change existing behavior or scope in an ongoing project. Identifies the affected docs and code before implementing, updates them together with the change, and records the change in the feature changelog.
License
MIT
Instructions
28 lines in SKILL.md · view on GitHub

Agent Skills spec issues

  • files: referenced but missing: references/tech-gate.md, references/docs-map.md, references/verification.md

Files (2)

  • SKILL.md
  • openai.yaml · agents/

SKILL.md (first lines)

# Zno-Change — Behavior / Scope Change

`<skills-root>` below means the directory containing all zno-* skills (e.g. `~/.claude/skills` or `~/.agents/skills`).

## Workflow

1. Restate the requested change briefly. Classify it: behavior change, scope change, UX adjustment, or data/rule change.
2. Before touching code, identify the affected surface: which docs describe the current behavior, which modules implement it, and what depends on it.
3. Ask clarification questions only if the change affects scope, business rules, data shape, permissions, technical decisions, deployment, or acceptance. Never invent unknown business rules.
4. If the change requires a major technology choice, apply the technical selection gate from `references/tech-gate.md` first.
5. If the project has a test framework configured, follow TDD: adjust or add a failing test for the new behavior, implement minimally, refactor under green tests. Skip TDD for pure UI tweaks, docs, or config changes.
6. Update the affected docs before or alongside the code change (impact → doc mapping in `references/docs-map.md`). If a required doc does not exist yet, scaffold it first:

   ```bash
   python <skills-root>/zno-init/scripts/init_project_docs.py <project-root> --scaffold <trigger>
   ```

7. Always update `docs/development/03-feature-changelog.md` after the change — including behavior removals.
8. Before marking the task complete, satisfy the verification gate in `references/verification.md` (at least 2 pieces of evidence).
9. If the change affects user-visible UI or browser workflows, the final response must include page-level manual test steps (template in `references/verification.md`).

## Shared references (read only when needed)

- `<skills-root>/zno-init/references/docs-map.md` — full doc set, doc update rules, scaffold triggers.
- `<skills-root>/zno-init/references/tech-gate.md` — technical selection gate and performance-aware design.
- `<skills-root>/zno-init/references/verification.md` — verification gate and final-response page test steps.

From 1447751897/ai-project-command-skills, MIT.

More from 1447751897/ai-project-command-skills

Signals

Stars
2
Forks
0
Open issues
0
Last commit (this folder)
Jul 2, 2026 (4 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from 1447751897

Done for you

Rather not set it up yourself?

Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.

See how we build AI agents →Read the case studies

Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.

launches shipped
50+
launches shipped
media placements
500+
media placements
founders on every account
2
founders on every account

Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block

Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.

Get zno-change running in your business

Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.

Goes to the Chalk Labs founders, not the newsletter. Privacy

Need help deploying zno-change?

CallGet help
Cite this page

zno-change skill. Agent Mart. https://agentmart.dev/skills/1447751897-zno-change (last updated 2026-10-24)