القائمة
Prioritization frameworks (RICE, MoSCoW) and capacity planning tools for Sprint structuring. Determines optimal Sprint groupings based on team velocity and dependency constraints.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Audit and review current JIRA sprint backlog progress by scanning _SPRINT.md and STORIES.md files. Generates progress tracking reports with completion rates and risk analysis. Triggers: check progress, review backlog, tiến độ sprint, kiểm tra backlog, sprint review, audit tasks.
Quét mã nguồn thực tế và cập nhật Project_Structure.md + summaries/ để PM_REVIEW luôn khớp với code hiện tại. Dành cho PM/AI agent quản lý cấu trúc dự án HealthGuard. Kích hoạt khi: "check project", "cập nhật cấu trúc", "kiểm tra source", "project thay đổi chưa?", "sync lại PM", "update summaries", "review structure", "kiểm tra project", "project còn đúng không?", "check source", "update structure".
Perform a detailed evaluation of a specific feature — analyze actual source code against architecture standards, verify SRS compliance, assess implementation quality, and cross-check JIRA Stories for the project development team. Use when user says "review code", "đánh giá chi tiết", "evaluate feature", "check implementation", "review module", "review chức năng", "kiểm tra code", "detailed review", "danh gia chi tiet", "xem code giúp", "chấm điểm code", "review feature", "score this module". DO NOT use for: PR reviews, debugging, writing new code, generating test cases.
Implement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design. Use when architecting complex backend systems or refactoring existing ...
Automatically generate or draft standards-compliant SRS (Software Requirements Specification) and SDD (Software Design Document - IEEE-1016-2009) from source code and requirements. Utilizes a multi-agent brainstorming model with Architect and BA roles to cross-review and produce the documentation. Use when the user requests "write SRS", "write SDD", "create IEEE-1016-2009 template", "generate design document", "generate system design document".
Comprehensive toolkit for product managers including RICE prioritization, customer interview analysis, PRD templates, discovery frameworks, and go-to-market strategies. Use for feature prioritizati...
| name | product-manager-toolkit |
| description | Prioritization frameworks (RICE, MoSCoW) and capacity planning tools for Sprint structuring. Determines optimal Sprint groupings based on team velocity and dependency constraints. |
Apply structured prioritization frameworks to rank tasks, group them into optimal Sprints, and ensure capacity constraints are respected.
RICE Score = (Reach × Impact × Confidence) / Effort
Reach: Number of users affected per Sprint
Impact:
- Massive = 3x (core product functionality)
- High = 2x (important feature)
- Medium = 1x (useful addition)
- Low = 0.5x (minor improvement)
- Minimal = 0.25x (cosmetic)
Confidence:
- High = 100% (well-defined UC, clear requirements)
- Medium = 80% (some ambiguity)
- Low = 50% (exploratory, unclear scope)
Effort: Story Points
| Category | Description | Action |
|---|---|---|
| Must Have | MVP-critical, system won't work without it | Sprint 1-2 |
| Should Have | Important but system works without it | Sprint 2-3 |
| Could Have | Nice to have, enhances experience | Sprint 3-4 |
| Won't Have | Out of scope for current release | Backlog |
Inputs:
Capacity formula:
Available SP = Team Velocity × 0.8 (buffer)
= 32 × 0.8 = ~26 effective SP
If Sprint has heavy infra tasks: allow up to 42 SP (Sprint 1 pattern)
If Sprint has integration-heavy tasks: cap at 26 SP
Grouping rules:
Sprint allocation table:
| Sprint | Theme | Epics | Total SP | Rationale |
| ------ | --------------- | --------- | -------- | ------------------------------ |
| 5 | Admin Dashboard | EP17-EP19 | ~38 | Dependencies resolved in S1-S4 |