agentleFS
Sign inStart free
rpraharajrpraharaj/ai-sdlc/skills/triage-blockers/SKILL.md

triage-blockers

Skill0 starsChanged 18 days agoMITView on GitHub

Cluster blockers, name an owner, and escalate per decision-rights. Use when the user asks to triage blockers, stand-up blockers, or /triage-blockers. Do not invent owners. Update RAID rather than a second list.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not keep a second blocker database.

    line 19
  2. Very specific:

    If RAID is missing and the user has no list, stop and offer update-raid.

    line 34
  3. Distinctive:

    Read AGENTS.md if present.

    line 43

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

Triage blockers

Cluster and escalate. This is not update-raid (that writes the log) and not assess-change.

Do not keep a second blocker database. Prefer RAID ids.

Is this the right skill?

SignalDo this instead
Add a risk with evidenceupdate-raid
Scope/date changeassess-change
Weekly pagewrite-status after this

Required inputs

  • Open issues/dependencies from docs/govern/raid.md and/or stand-up notes the user provides
  • context/decision-rights.md

If RAID is missing and the user has no list, stop and offer update-raid.

Human decisions (do not invent)

  • Owner if not on the RAID row
  • Escalate vs wait

Procedure

  1. Read AGENTS.md if present. Read RAID and decision-rights.
  2. Cluster open issues/dependencies by theme (same system, same team).
  3. Find the home: docs/govern/blockers-YYYY-MM-DD.md and tell the user to persist owners on RAID via update-raid.
  4. Open references/blockers-template.md. Copy every heading. Write n/a when unused.
  5. Each cluster: RAID ids, owner (from RAID or unassigned), escalate to (from decision-rights) or none.

Output

  • Path: docs/govern/blockers-YYYY-MM-DD.md
  • Template: references/blockers-template.md

Quality bar

  • Every cluster cites RAID ids or a user-named source
  • No invented owner
  • Escalate targets come from decision-rights or none
  • Unused headings are n/a

Done

  1. Path
  2. Cluster count
  3. Next skill: update-raid then write-status

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.

Check your setup, free