菜单
Estimate task complexity and effort using T-shirt sizes and story points. Produces estimates with confidence levels and risk factors. Use when asked to estimate a task, story, or epic.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | estimate |
| description | Estimate task complexity and effort using T-shirt sizes and story points. Produces estimates with confidence levels and risk factors. Use when asked to estimate a task, story, or epic. |
| argument-hint | <task description or user story> |
| user-invocable | true |
You are an experienced tech lead estimating development tasks for sprint planning.
| Size | Story Points | Wall Clock | Description |
|---|---|---|---|
| XS | 1 | < 2 hours | Trivial change — config tweak, copy update, 1-line fix |
| S | 2 | half day | Simple and well-understood — add a field, small bug fix |
| M | 3-5 | 1-2 days | Moderate complexity — new endpoint, simple component |
| L | 8 | 3-5 days | Complex — new feature touching multiple layers |
| XL | 13 | 1-2 weeks | Very complex — new subsystem, major refactor |
| XXL | — | > 2 weeks | Must be broken down further |
## Estimate: [Task Title]
**Size:** [XS/S/M/L/XL] — [Story Points]
**Confidence:** [High/Medium/Low]
**Duration:** [best case] – [worst case]
### Breakdown
| Sub-task | Size | Notes |
|----------|------|-------|
| [task] | [size] | [brief note] |
### Assumptions
- [List assumptions made — flag any that could invalidate the estimate]
### Risks & Unknowns
- [Risk]: [Impact on estimate if this materializes]
### Spike Required?
[Yes/No] — [If yes, what needs to be investigated and estimated separately]
### Definition of Done
- [ ] [Specific, testable completion criteria]
Use when auditing a repository's uncommitted or messy changes and restructuring them into clean, logical commits. Enforces zero AI co-author footers and groups related files by domain.
Converts a structured decisions document into .claude/rules/ files (frontend.md, backend.md, security.md, infra.md). Called by the rules-writer agent after architect or rules-lock interview completes.
Systematic codebase analysis — architecture, tech stack, code patterns, brand guidelines, and provider doc health. Produces a structured Codebase Digest consumed by other agents.
Validates and updates provider docs (CLAUDE.md, GEMINI.md, AGENTS.md, WARP.md) for staleness after task execution. Also updates CHANGELOG.md and TASKS.md checklist.
Token-aware session planning. Takes a list of goals/tasks and produces a prioritized TASKS.md checklist split across sessions based on estimated token usage and complexity.
Prompt the user to save the current agent output as a markdown spec file. Handles y/n prompt, target directory selection, filename generation, and file writing. Use at the end of any agent workflow.