agentleFS
redhat-developerredhat-developer/rhdh-skills/skills/jira/rhdh-prepare-refinement/SKILL.md

rhdh-prepare-refinement

Skill20 starsChanged 20 days agoApache-2.0View on GitHub

Intelligent refinement brief for RHDH scrum teams. Analyzes the queue, surfaces non-obvious risks (scope unclear, blockers, stale work, timeline unrealistic), identifies patterns, and makes recommendations about what to discuss. Say "prepare refinement for Install on 2.1.0" and get actionable insights, not field validation. Use for "prepare refinement", "refinement prep", or "what should we discuss in refinement for [team] on [version]".

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If either is missing, ask.

    line 25

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Prepare RHDH refinement

Route

Load workflows/prepare-refinement.md.

Inputs

  1. Team — e.g. "Install", "Plugins", "Frontend". Resolve the board ID from /rhdh-jira-api (references/jql-patterns.md, Boards table).
  2. Fix version(s) — e.g. "2.1.0" or "all 2.1.x and 2.2.0". Scopes the queue.

If either is missing, ask.

Boundary with the neighbouring skills

  • Per-issue exit-criteria checks, duplicates, comments → /rhdh-jira-refine.
  • Sprint planning from refined work → /rhdh-jira-sprint-plan.
  • Opening new issues → /rhdh-jira-create.
  • Release-wide status across all teams → /rhdh-release-status.

Completion

Complete when the refinement brief is printed to the conversation with analyzed issues, identified risks, and actionable recommendations. No files written, no Jira state modified.

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.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

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.