菜单
Guide for calculating and explaining task priority scores
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Git commit conventions and workflow
Guide for breaking features into atomic, implementable tasks
TDD workflow and testing patterns
Author safe RalphX Agent Workflow scripts that orchestrate durable delegated agents through the high-level workflow API.
Guide for analyzing git diff and refining QA test plans
Guide for generating QA test steps with agent-browser commands
| name | priority-assessment |
| description | Guide for calculating and explaining task priority scores |
This skill helps calculate meaningful priority scores for tasks based on multiple factors.
Priority scores range from 0-100 and are calculated from five factors:
Priority Score = Dependency (30) + Critical Path (25) + Business Value (20) + Complexity (15) + User Hints (10)
How many other tasks does this task block?
| Blocks | Score | Reasoning |
|---|---|---|
| 0 tasks | 0 | No other tasks waiting on this |
| 1 task | 10 | Minor blocker |
| 2 tasks | 18 | Moderate blocker |
| 3 tasks | 24 | Significant blocker |
| 4+ tasks | 30 | Critical path item |
Example: "Create auth context" blocks login, logout, protected routes, and session persistence = 30 points
Is this task on the longest path to completion?
| Position | Score | Reasoning |
|---|---|---|
| Not on critical path | 0 | Can be done in parallel |
| On critical path, short | 10 | Part of main sequence |
| On critical path, medium | 18 | Important stepping stone |
| On critical path, start | 25 | Must be done first |
Example: "Define database schema" at the start of data layer critical path = 25 points
How much value does this deliver to users/stakeholders?
| Value | Score | Indicators |
|---|---|---|
| Low | 0-5 | Technical debt, internal only |
| Medium | 6-12 | Incremental improvement |
| High | 13-17 | Core functionality |
| Critical | 18-20 | User-facing, revenue-impacting |
Keywords that suggest high value:
Example: "Add payment processing" = 20 points (revenue-critical)
Simpler tasks should be done first (higher priority) when other factors are equal.
| Complexity | Score | Characteristics |
|---|---|---|
| Trivial | 15 | <30 min, config change |
| Simple | 12 | 1-2 hours, single file |
| Moderate | 8 | 2-4 hours, multiple files |
| Complex | 4 | 4+ hours, architecture |
| Very Complex | 0 | Multi-day, high risk |
Reasoning: Quick wins build momentum and reduce backlog.
Example: "Fix typo in error message" = 15 points (trivial fix)
Did the user express urgency or importance?
| Signal | Score |
|---|---|
| Explicit "urgent", "ASAP", "critical" | 10 |
| "Important", "need this soon" | 7 |
| "Nice to have", "eventually" | 2 |
| No signal | 5 (neutral) |
Example: "We need this for the demo next week" = 10 points
Map scores to priority levels:
| Score Range | Level | Action |
|---|---|---|
| 85-100 | Critical | Do immediately |
| 65-84 | High | Do soon |
| 40-64 | Medium | Normal queue |
| 20-39 | Low | When time permits |
| 0-19 | Trivial | Backlog |
Task: "Create user authentication context"
Factor Analysis:
Total: 30 + 25 + 18 + 8 + 7 = 88/100 (Critical)
Reason: "Critical blocker for authentication chain. Must be completed first to unblock login, logout, and protected routes. Moderate complexity but high value - enables all user-specific features."
When explaining priority to users:
[Task Title] - Score: [X]/100 ([Level])
This task scores [high/medium/low] because:
- [Key factor 1]: [explanation]
- [Key factor 2]: [explanation]
[If blocking]: This must be done before [dependent tasks].
[If blocked]: This depends on [blocker tasks] being completed first.
Infrastructure and types typically score high due to dependency factor:
When dependencies are equal, prioritize user-facing work:
Simple, high-value tasks should be prioritized:
Don't:
Do: