skills.rest
1447751897
1447751897COMMUNITY
Explore all skills by this author →
GitHub

zno-change

Evaluate and document controlled requirement changes in ongoing projects.

2|Updated Jun 17, 2026
Search Tags:#project management#documentation#verification#test-driven development#requirement change
One-click install
npx skills add https://github.com/1447751897/ai-project-command-skills --skill zno-change
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: zno-change
Source: https://github.com/1447751897/ai-project-command-skills/tree/main/skills/zno-change
Command: npx skills add https://github.com/1447751897/ai-project-command-skills --skill zno-change

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python, and includes scripts (resource) and references (resource) components.

What problem does it solve?

The zno-change skill solves the problem of assessing and documenting requirement changes in an ongoing project, ensuring changes are implemented with proper documentation and verification.

Core Features & Use Cases

  • Controlled Change Assessment: Identifies the affected documentation and code before implementing changes.
  • Documentation: Updates affected documents and records changes in the feature changelog.
  • Verification: Ensures the change meets verification standards with at least 2 pieces of evidence.
  • Technical Selection: Applies a technical selection gate for major technology changes.
  • TDD: Adheres to Test-Driven Development principles when necessary.

Quick Start

Use the zno-change skill to implement a requirement change and document it.

Frequently Asked Questions about zno-change

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I assess and document requirement changes in an ongoing project?▼

Requirement changes are assessed by identifying affected documentation and code, applying technical selection gates, and recording updates in the feature changelog to ensure controlled implementation.

What is the best way to ensure verification compliance for requirement changes?▼

Verification compliance for requirement changes is ensured by collecting at least two pieces of evidence and adhering to Test-Driven Development principles during the implementation process.

Does requirement change documentation work with Python scripting and Markdown?▼

Yes, requirement change documentation utilizes Python scripting for technical gates and Markdown documentation tools to update affected documents and maintain the feature changelog.

When do I need to apply a technical selection gate for requirement changes?▼

A technical selection gate for requirement changes must be applied when introducing major technology changes to evaluate their impact before updating documentation and code.

How to update affected documentation and code when implementing a requirement change?▼

To implement a requirement change, identify the affected documentation and code, apply technical gates, update the affected documents, and record all modifications in the feature changelog.

Related Skills

Explore More Software Engineering Skills→
az9713az9713

dark-code-suite-init

Initialize a project with dark code prevention directories, CLAUDE.md section, and baseline audit.

Community
Intermediate
yocxy2yocxy2

qa-only

Test web applications and generate structured bug reports with health scores.

Community
Intermediate
sumpalabssumpalabs
10

to-prd

Synthesize project conversations and codebase context into structured PRDs.

Official
Intermediate
t0labt0lab
2

quality-gates

Run project verification commands and report exit codes after code changes.

Official
Basic