convert-effort-days-to-calendar-time
Use when a day-by-day work estimate is being read as elapsed days. Applies a focus factor for meetings, interruptions and on-call so the effort total becomes a realistic calendar duration.
- License 许可
- MIT
- 最近更新
- 2026-11-13
- Stars
- ★ 81
- Forks
- 17
01 前言 Front Matter
- name
- convert-effort-days-to-calendar-time
- description
- Use when a day-by-day work estimate is being read as elapsed days. Applies a focus factor for meetings, interruptions and on-call so the effort total becomes a realistic calendar duration.
02 资源文件 3
- 许可证LICENSE1.0 KB
- 参考文档SOURCE.md362 B
- 参考文档TRUST.auto.yaml2.2 KB
03 SKILL.md 正文
Convert effort days to calendar time
One "dev-day" of work is not one calendar day. Meetings, interruptions, reviews and on-call eat the clock, and a 20-effort-day plan quietly becomes six weeks. Convert explicitly, with a factor you can defend.
Procedure
-
Start with raw effort: sum the task durations in person-days, e.g. 20 person-days.
-
Pick a focus factor — the fraction of a working day spent on the actual task, logged in
notes/capacity.md. Realistic values run 0.5–0.8; a person juggling on-call or two projects sits near 0.5. -
Divide effort by the available-fraction to get calendar days per person:
python3 -c "effort=20; focus=0.7; print('calendar days', round(effort/focus,1))" calendar days 28.6 -
Subtract known non-work days in the window: public holidays, a team offsite, release freeze. Do not assume a five-day week.
-
Account for people, not just days. Two people on independent work nearly halve the time; two on the same small task do not (coordination cost) — model parallel work as a chain only when the pieces are truly independent.
-
If the window includes a person's holiday, reduce their availability rather than pretending they are full-time.
Record each person's factor separately; a team average hides whoever is effectively part-time.
-
Recompute after any schedule change; the factor is a property of the environment, not a constant.
Pitfalls
- Reporting effort days as calendar days, the single most common source of "but you said two weeks."
- Using focus factor 1.0 for a person who is on-call or pairing, which is never achievable.
- Assuming a 5-day week and 8 productive hours; realistically 6 or fewer hours are deep-work.
- Splitting one small task across three people to "compress" it, when coordination makes it slower.
- Forgetting that the estimate itself and code review consume the same hours, not extra ones.
Verification
python3 -c "print(round(20/0.7,1), 'vs', 20)"
# 28.6 vs 20 — the calendar duration is longer than the effort; report both
Report effort days, the focus factor used and why, and the resulting calendar duration with holidays removed.
04 同仓库更多 Skills
recipe-performance
Diagnose a specific MetaMask user flow's real-app performance and Sentry critical-user-flow telemetry with deterministic mm-harness recipes. Use for CUF boundaries, cold/warm/background-resume behavior, latency regressions, lifecycle tags, duplicate or blocking network requests, long tasks, layout/paint cost, screen redraws, React rerenders, or browser trace analysis where tests alone cannot prove the real app.
mexc-spot-websocket
MEXC Spot WebSocket workflows for public streams, protobuf handling, depth maintenance, listen keys, and private streams without exposing API keys.
mexc-spot-rest
MEXC Spot REST workflows for public data, signed account requests, orders, wallet/admin actions, and secure signing without exposing API keys.
mexc-futures-websocket
MEXC Futures WebSocket workflows for public streams, private account/order/position streams, ping/pong, subscriptions, and depth maintenance.
0xklen-version-and-refresh-sanctions-lists
暂无简介
verify-tests-cover-changed-lines
Use when a PR adds code that the existing suite may not exercise. Measures patch coverage — the share of newly changed lines hit by tests — before approving.