القائمة
Use when the team has sized work and must choose a realistic iteration scope, sequence, and ownership model that fits capacity and current risk.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when a bug, failing test, regression, or unexpected behavior needs a root-cause-first debugging loop before code changes, especially when brownfield seams, recent releases, or historical defect matches make guesswork unsafe.
Use when E2E tests must go beyond shallow happy-path checks — multi-step user journeys, stateful sessions, cross-boundary state consistency, failure-mode edges — or when the suite passes but production still breaks. Platform- and framework-agnostic (web, mobile, desktop; Playwright, XCUITest, Cypress).
Use when discovery has narrowed an idea enough that the team must make a go/no-go, pivot, or scope-down decision based on technical, economic, operational, or timeline viability before requirements, architecture, or major implementation.
The mandatory gateway for all new engineering work. Triage and route new products, apps, features, migrations, tech-debt, or any 'not sure where to start' request to the correct lifecycle path. Use before starting design or implementation. Do not use for ongoing tasks, specific debugging, or PR reviews.
Use when discovery needs evidence about market demand, competitors, pricing pressure, or underserved segments for a new product or expansion idea before feasibility, user research, or requirements are finalized.
Use when intake has identified the likely lifecycle path but the problem statement, solution direction, or key trade-offs are still too fuzzy for requirements, research, or architecture work to start cleanly
| name | pc-sprint-planning |
| description | Use when the team has sized work and must choose a realistic iteration scope, sequence, and ownership model that fits capacity and current risk. |
| metadata | {"phase":"03-planning","inputs":["task-list","estimate-set","risk-register"],"outputs":["sprint-plan"],"prerequisites":["pc-estimation"],"quality_gate":"Sprint scope matches capacity, dependencies and risks are visible, and the team can explain why this slice is achievable now","roles":["tech-lead","product-manager"],"methodologies":["all"],"effort":"small"} |
Choose the next iteration on purpose. A sprint plan is a capacity-constrained bet, not a wish list.
Sprint planning turns a backlog of valid work into a realistic short-horizon commitment.
See context and anti-pattern notes.
I/O contract notes define required inputs and authority.
Confirm the real capacity for the iteration: available people, external blockers, carry-over work, and operational load. Adjust for on-call or release overhead when relevant.
Choose the smallest set of tasks that:
Document:
The output should let anyone understand what the team is betting on, what was deferred, and which risks or assumptions could force replanning mid-sprint.
Produce only declared outputs at their documented quality boundary.
