pr-plan-bucket-triage-before-sizing SKILL.md skillA
pr-plan-bucket-triage-before-sizing from wan-huiyan/agent-traffic-control is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add wan-huiyan/agent-traffic-control/pr-plan-bucket-triage-before-sizing@v1.0.0Pins v1.0.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- wan-huiyan/agent-traffic-control
- Path
plugins/agent-traffic-control/skills/pr-plan-bucket-triage-before-sizing/SKILL.md- Versions recorded
- 5
- Latest version
- v1.0.0, committed Aug 12, 2026
- First version recorded
- Aug 10, 2026
- Size
- 14,645 bytes
- Repository stars
- 3
- License
- MIT
Before writing detailed pull request plans against a codebase you have not audited, triage it by bucket so sizes rest on findings rather than assumptions.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Phase 0 Bucket Triage Before Writing PR Plans ## Problem `superpowers:writing-plans` produces detailed task-by-task plans with exact file paths, LOC estimates, and TDD steps. That's the right output when you **know the codebase state** — but a common failure mode is writing those plans on assumptions about: which routes already exist, whether a colleague's in-flight module is a stub or substantial, what storage convention links results to runs, whether a "known defect" is still real or was quietly fixed. You burn cycles writing detailed plans, the engineer starts implementing, and within the first hour they discover the plan was sized against a codebase that doesn't exist. The fix is **always re-plan with the new evidence** — meaning the original plan was waste. The cost of writing plans on speculation is asymmetric: - Writing 4 detailed plans on speculation: ~2 hours. - Discovering plan-1 was wrong during implementation, re-planning, re-discussing with reviewer: ~4 hours per wrong plan. - Net cost of speculation: ~14 hours. - Cost of a 1-day Phase 0 triage: ~6 hours. - Net savings: ~8 hours, AND the surviving plans are sized in concrete LOC …
Read the whole file at its exact version.
How to install
mdr add wan-huiyan/agent-traffic-control/pr-plan-bucket-triage-before-sizing@sha256:b5347d1b8e98c8e1The line at the top of this page pins the label v1.0.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_4awxof4gcffpvaiw)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Aug 10, 2026 and Aug 12, 2026, more than one a day.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.0 latest | 2026-08-12 | 5811428 | 14,645 B | A | view · diff |
| v1.0.0 | 2026-08-11 | f274e4b | 14,747 B | A | view · diff |
| v1.0.0 | 2026-08-10 | 5b6d8a2 | 14,703 B | A | view · diff |
| v1.0.0 | 2026-08-10 | a58c34c | 14,680 B | A | view · diff |
| v1.0.0 | 2026-08-10 | a39e221 | 16,034 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (14645 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
wan-huiyan/agent-traffic-control · 3 stars · license MIT · pushed 2026-09-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_4awxof4gcffpvaiw GET https://markdownregistry.com/api/v1/resolve?ref=wan-huiyan/agent-traffic-control/pr-plan-bucket-triage-before-sizing GET https://markdownregistry.com/api/v1/blob/b5347d1b8e98c8e16d2d240aac7cdfba59bf4514a7c84e7353cf0d8daa91396b
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.