Estimate how long a dev task will really take when it's built AI-assisted (an agent writes the code, a human reviews, tests, ships). Grounds every number in the actual code first, counts agent work in tool-call rounds, then adds the human layer (diff review, local run, browser QA, PR/CI, review feedback, PM back-and-forth) as separate lines. Use this whenever someone asks for an estimate, "how long would X take", "how many hours", sizing, scoping, a quote for a PM or client, or a comparison of options by effort — even when they don't say "estimate" and even for a quick ballpark. Also use it before replying to a ticket, Lobby/Teamwork/Slack thread or PR comment that asks "estimate to complete?". Adapted from ZhangHanDong/agent-estimation (MIT).
1 skill
Render audit findings as a designed, paginated A4 PDF report with a cover page, severity donut and category bar charts, colored severity chips, evidence-backed strengths, prioritized recommendations, and copy-ready GitHub issue blocks.
1 skill
Babysit a GitHub PR from review all the way to MERGED.
1 skill
Turn a settled scope into an implementation plan at docs/plans/NNNN-<slug>.md: files affected, phased sequence gated on numbered acceptance examples, edge-case ledger, rollback and risk. Consumes PRDs + ADRs. Formerly heist.
1 skill
Maintain a monthly brag document and roll it up into a promo packet, self-review, CV material or interview story seeds. Lucas Faria's 4-field template + Julia Evans' impact-first categories, with ownership, status, evidence and story seeds recorded each month. Feeds cv-craft.
1 skill
Build a one-page business brief on a company the user is about to work for or with, so they walk in knowing how it makes money and where their work moves the number.
1 skill