القائمة
Prioritize software project work items using impact, urgency, dependencies, risk, and effort analysis. Use when planning milestones, ordering backlog items, or deciding what to work on next.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Design software system architecture using requirements, constraints, data models, APIs, integrations, dependencies, and technical tradeoff analysis. Use when deciding how a system or feature will fundamentally work.
Break software milestones, features, epics, requirements, and architecture plans into executable stories, tasks, and subtasks with clear boundaries and acceptance criteria.
Analyze software project dependencies, blockers, prerequisite work, critical paths, ownership constraints, external dependencies, and sequencing risks. Use when preventing execution deadlocks or delivery surprises.
Estimate software project effort, complexity, uncertainty, capacity, cost, and delivery ranges using scoped work, decomposed tasks, dependencies, and implementation risk.
Define measurable outcomes, KPIs, success criteria, acceptance thresholds, and decision criteria for software products, features, projects, or initiatives. Use when establishing what success looks like.
Generate and frame software product or feature ideas using user problems, market signals, constraints, and opportunity analysis. Use when brainstorming, discovering opportunities, or deciding what should exist and why it matters.
| name | prioritization |
| description | Prioritize software project work items using impact, urgency, dependencies, risk, and effort analysis. Use when planning milestones, ordering backlog items, or deciding what to work on next. |
This skill helps evaluate and rank software work items so execution order maximizes leverage, reduces blockers, and aligns with project goals.
Use this skill when:
Expected inputs:
Work items should ideally include:
Inputs usually come from scoping, goal-setting, or decomposition. If the
items are too large or unclear, use decomposition before prioritizing.
Always optimize for:
Avoid optimizing solely for:
Convert incoming work into a consistent structure.
Required fields:
Flag missing or ambiguous information.
Determine:
Highlight tasks that unblock many others.
Evaluate each item across:
| Factor | Questions |
|---|---|
| Impact | How valuable is this if completed? |
| Urgency | What happens if delayed? |
| Effort | How expensive is implementation? |
| Risk Reduction | Does this reduce operational or technical risk? |
| Dependency Value | Does this unblock additional work? |
| Reversibility | Is this decision expensive to undo later? |
Suggested scoring:
Suggested heuristic:
priority_score =
(impact * 5)
+ (urgency * 4)
+ (risk_reduction * 3)
+ (dependency_value * 4)
- (effort * 2)
Use judgment instead of blindly following numeric scores.
Suggested labels:
| Priority | Meaning |
|---|---|
| critical | Immediate attention required |
| high | Important for near-term execution |
| medium | Valuable but not blocking |
| low | Opportunistic or cosmetic |
Critical items usually include:
Generate:
Output format:
# Prioritized Backlog
## 1. Replace insecure authentication
Priority: Critical
Why:
- High security exposure
- Blocks enterprise rollout
- Large downstream impact
Next action:
- Begin implementation immediately
- Schedule security review
Avoid:
Before finalizing prioritization:
Escalate when:
Input:
Expected ordering: