agentleFS
Sign inStart free
danielvm-gitdanielvm-git/bigpowers/skills/change-request/SKILL.md

change-request

Skill288 starsChanged 5 days agoMITView on GitHub

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.

6 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Draft: Add story + tasks[] with Gherkin-style AC in epic YAML (each task has verify).

    line 25
  2. Distinctive:

    If the user's request is in natural language and does not match the structured format of Mode A or Mode B, enter Conversational Mode to …

    line 47
  3. Very specific:

    Run bash scripts/sync-status-from-epics.sh.

    line 59

“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
<!-- story: e45s29 --><!-- story: e20s01 -->

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 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

If the user's request is in natural language and does not match the structured format of Mode A or Mode B, enter Conversational Mode to extract the change parameters through interactive dialogue.

5-Step Flow

  1. Capture: Parse the natural-language request for what, why, and where. Ask at most 3 clarifying questions before drafting.
  2. Locate: Identify which epic or capability in specs/epics/ the request affects or replaces.
  3. Draft: Present a structured draft of the proposed story and tasks for user confirmation.
  4. Score: Estimate the WSJF score and explain the calculation so the user understands the priority.
  5. Place: Confirm the final epic placement with the user before writing files.

After either mode

Run bash scripts/sync-status-from-epics.sh. Suggest plan-work or build-epic for the top-ranked unstarted story.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free