What is req-change-workflow?

A step-by-step process for changing a feature that already exists and runs. It requires checking the current code, agreeing on the design, making a small change, testing it, and recording the decision.

Use it to plan and implement changes to existing features, especially when they involve permissions, authentication, stored data, configuration, or multiple files.

It reduces accidental changes, unclear scope, and difficult rollbacks when a requirement affects several parts of an application.

req-change-workflow — Skill for Claude Code and Codex by yunshu0909

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add yunshu0909/yunshu_skillshub --skill req-change-workflow

Clone the repo

git clone --depth 1 https://github.com/yunshu0909/yunshu_skillshub

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/yunshu0909/yunshu_skillshub/req-change-workflow/github.svg)](https://agentmods.dev/skills/yunshu0909/yunshu_skillshub/req-change-workflow)

Your own site

<a href="https://agentmods.dev/skills/yunshu0909/yunshu_skillshub/req-change-workflow"><img src="https://agentmods.dev/badge/skills/yunshu0909/yunshu_skillshub/req-change-workflow/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/yunshu0909/yunshu_skillshub/req-change-workflow"><img src="https://agentmods.dev/badge/skills/yunshu0909/yunshu_skillshub/req-change-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 340 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,420 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00340	$0.01420
Opus 5.5	$0.00136	$0.00568
Sonnet 5.5	$0.00068	$0.00284
Haiku 4.5	$0.00034	$0.00142

Measured 1mo ago against content hash 6c29e0220f93, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

req-change-workflow scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/impact_scan.sh), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

coding/req-change-workflow/SKILL.md · 114 lines

How it starts

The opening of the file, as written. The whole thing — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Req Change Workflow

Overview

Use a lightweight, repeatable workflow to modify an existing requirement without scope creep or “边改边炸”. Produce clear artifacts at each gate so the user can approve before the implementation starts.

Workflow (gated loop)

Follow the steps in order. Do not implement code changes until the user approves Step 4.

Step 0: Set the plan (optional but recommended)

Use update_plan to create 5–7 short steps: clarify → baseline → impact → design → implement → validate → document.
Keep exactly one step in_progress at a time and advance as you finish.

Step 1: Clarify the change (lock scope first)

Ask the user for the minimal inputs, then rewrite them into a clear “change brief”:

Target (1 sentence): what outcome changes.
Out of scope (1 sentence): explicitly what must NOT change.
Acceptance criteria (3–6 bullets): observable behaviors that can be verified.
“Must keep” constraints: compatibility, performance, security, no new dependencies, no network, etc.
Rollback expectation: can we revert by reverting a diff, or does it require data migration/backfill?

Use the template in references/change-brief-template.md.

Step 2: Confirm current behavior from code (baseline)

Do not trust memory or assumptions. Locate the real entrypoints + current data flow and summarize it in 5–10 lines:

UI entrypoints (e.g., sidepanel/, options/) and where user actions are wired.
Background orchestration (e.g., service_worker.js).
Core modules (e.g., src/core/...) and storage (src/core/local/...).
Config/permissions changes (e.g., manifest.json).

For Chrome extension projects, scripts/impact_scan.sh can help locate likely files. For other projects, use their actual entrypoints and search tools. Then read the relevant implementation to confirm behavior.

Output artifact: “Current behavior summary” + a short file list (with why each file matters).

Step 3: Impact + risk assessment (change budget)

Before proposing a new design, list:

Read the full file on GitHub · 114 lines

Files

What ships with it

5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

1mo ago Changed · +4 lines · +8 tokens per session 6c29e0220f93
2mo ago First seen · 110 lines · 332 tokens per session scan A fc6cc5166d4f

Subscribe to this mod's changes

req-change-workflow is a skill published in the GitHub repository yunshu0909/yunshu_skillshub (789 stars, last pushed 26d ago), licensed MIT. It adds 340 tokens to every session and 1,420 once invoked, about $0.0014 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Planning

req-change-workflow next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
req-change-workflowyunshu0909/yunshu_skillshub	Skill	789	26d ago	MIT	A	340	Claude Code, Codex
imagegenopenai/codex	Skill	133k	yesterday	Apache-2.0	A	113	Codex
playwright-climicrosoft/playwright	Skill	99k	yesterday	Apache-2.0	A	19	Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	4d ago	MIT	A	200	Claude Code, Codex
systematic-debuggingobra/superpowers	Skill	313k	3d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	95	Claude Code
next-partial-prefetching-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	103	Claude Code