Change Request
Add a new requirement or reorder epics by WSJF against specs/release-plan.yaml and epic capsule directories. Modes Add and Reorder. Use when a new requirement arrives mid-release or the plan needs prioritization.
Install
npx skills add danielvm-git/bigpowers --skill change-requestgit clone --depth 1 https://github.com/danielvm-git/bigpowers.git /tmp/bigpowers
mkdir -p ~/.claude/skills
cp -r /tmp/bigpowers/.cline/skills/change-request ~/.claude/skills/change-requestPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Change Request > **HARD GATE** — `specs/release-plan.yaml` must exist before running either mode. If it doesn't, run `plan-release` first. > > → verify: `test -f specs/release-plan.yaml` Two modes. State which one you want or the skill will ask. ## Mode A — Add Intake a new requirement mid-flight without disrupting work in progress. 1. **Capture**: What is the change? What problem does it solve? 2. **Locate**: Which existing stories in `specs/epics/` does it affect or replace? 3. **Draft**: Add story + `tasks[]` with Gherkin-style AC in epic YAML (each task has `verify`). Tag requirement deltas: `ADDED` / `MODIFIED` / `REMOVED` / `RENAMED` with before/after for non-`ADDED` changes (e45s29). 4. **Place**: Append story under existing epic capsule, or create `specs/epics/eNN-slug.yaml` and register in `release-plan.yaml` `epics[]`. 5. **Score**: Compute WSJF; note if it outranks in-progress work. → verify: `grep -c 'stories:' specs/epics/*/epic.yaml` ## Mode B — Reorder Value-engineering pass over the full release using WSJF. See [REFERENCE.md](REFERENCE.md) for the full WSJF scoring rubric. 1. **Score** each epic/story: BV + TC + RR / Job Size. 2. **Re-sort** `release-plan.yaml` `epics[]` and per-epic `wsjf` fields. 3. **Flag cut candidates**: WSJF < 1.5. 4. **Update** `specs/release-plan.yaml` and epic `wsjf` keys with rationale. 5. **Report** the delta. → verify: `grep -c 'wsjf' specs/release-plan.yaml specs/epics/*/epic.yaml` ## Conversational Mode
Details
- Skill name
change-request- Repository
- danielvm-git/bigpowers
- Path
.cline/skills/change-request/SKILL.md- License
- MIT
- Repo updated
- 9 November 2026
FAQ
What does the Change Request skill do?
Add a new requirement or reorder epics by WSJF against specs/release-plan.yaml and epic capsule directories. Modes Add and Reorder. Use when a new requirement arrives mid-release or the plan needs prioritization.
How do I install the Change Request skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add danielvm-git/bigpowers --skill change-request. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Change Request popular?
It lives in danielvm-git/bigpowers, which has 292 GitHub stars and 23 forks.
Related skills
Align Grid
292danielvm-git/bigpowers
Build editorial/magazine/report webpages on a GENUINE Müller-Brockmann modular grid (International Typographic Style) — not a decorative one. Encodes the discipline (columns + modules + baseline, grotesque type, flush-left, restrained black/white/red palette) AND the hard-won front-end engineering to make the grid real, visible, and verified: one CSS-variable source of truth, an interactive grid-toggle overlay that lives in the SAME content box as the content, subgrid "bands" so every element snaps to a column line, an 8px baseline lock, and runtime OPTICAL ALIGNMENT that puts display type's i
Assess Impact
292danielvm-git/bigpowers
Analyze the blast radius of a proposed change before any code is written. Maps dependents, affected stories, and test coverage. Produces specs/IMPACT_LATEST.md. Use before plan-work on any non-trivial change, when touching a shared module, or when the user asks "what does this break?".
Audit Code
292danielvm-git/bigpowers
Self-review checklist for the coding agent to run before dispatching a reviewer. Checks CONVENTIONS.md compliance, Boy Scout Rule, test coverage, types, and SOLID. Produces a pass/fail checklist. Use before request-review, before committing, or when user asks for a code quality check.
Consent and Agency
207Owl-Listener/ai-design-skills
Designing for informed user consent, opt-out, and human override.
Chain of Thought Design
207Owl-Listener/ai-design-skills
Designing reasoning chains that produce better outputs.
Context Engineering
207Owl-Listener/ai-design-skills
Designing what information goes into the context window and in what order.
Browse the most popular Claude skills, all other skills, or write your own with the skills generator.