菜单
Cap every task at ~60 minutes (default 30). Budget is fixed at creation. If overrun, stop, split leftover work into @todo puzzles, close the original with what's done. Use when estimating, planning, starting work, or when a task is running longer than budgeted.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
基于 SOC 职业分类
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/avidrucker/yegor-pm-skills --skill yegor-microtasks命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
Diagnose whether an incoming work-request — a casual task handed to an agent, a ticket, or an ask handed to a teammate — is clear enough to act on, before guessing. Runs a gate (request vs goal vs question vs complaint), counts how many materially-different deliverables the request could mean, and checks six concrete elements (target, now-state→outcome, done-check, acceptor, bounds), then emits the specific clarifying questions to close the gaps rather than fabricating a sharper version. Use when a handed-over task/request is genuinely ambiguous or visibly thin, or the user asks "is this clear enough to act on?", "what's missing from this ask?", "sharpen this request before we start" — lean toward firing on vague casual requests like "just make X better / less broken". NOT for personal goals (use assess-goal), already-filed GitHub issues (use issue-review-skill), or pure conceptual questions.
Project management and engineering-discipline skill set distilled from Yegor Bugayenko's XDSD methodology. Meta-orchestrator for 17 sub-skills (yegor-pdd, yegor-spikes, yegor-bdd, yegor-microtasks, yegor-tickets, yegor-architect, yegor-velocity, yegor-projections, yegor-nohelp, yegor-review, yegor-unit-tests, yegor-stuck, yegor-merge-gate, yegor-builds, yegor-simba, yegor-small-repos, yegor-personas). Triggers when planning work, breaking down tasks, managing issues, forecasting timelines, reviewing progress/code, writing tests, setting up CI/builds, handling blockers, capping work-in-progress, gating merges, deciding repo boundaries, evaluating a hard decision through multiple role lenses, or deciding on workflow approach.
Apply Yegor-style velocity discipline by measuring progress primarily as verified closed tickets per time window, not commits, hours, or lines of code. Use when Codex is reviewing project progress, answering "how is it going?", checking stale work, interpreting productivity, forecasting from measured closure cadence, or pushing back on misleading activity metrics.
| name | yegor-microtasks |
| description | Cap every task at ~60 minutes (default 30). Budget is fixed at creation. If overrun, stop, split leftover work into @todo puzzles, close the original with what's done. Use when estimating, planning, starting work, or when a task is running longer than budgeted. |
| version | 0.1.0 |
| last_reviewed | 2026-05-23T00:00:00.000Z |
Cap every task at ~60 minutes (default 30). Budget is fixed at creation. If overrun, stop, split leftover work into puzzles, close the original with what's done.
@todo #N:Mm) for the leftover work.Before starting work:
When the user says "let's just add X, Y, and Z":
When work overruns:
Weekly calibration:
yegor-pdd — overrun's leftover work goes into @todo puzzles.yegor-velocity — small tickets → cleaner closure cadence.yegor-architect — architect's job is to decompose into ≤60min units for couriers.research/philosophy_03_microtasks_microtasking.md