القائمة
Use when reviewed tasks exist and the team must size them with explicit assumptions, confidence, and risk awareness before committing to a timeline or sprint scope.
التثبيت باستخدام 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-estimation |
| description | Use when reviewed tasks exist and the team must size them with explicit assumptions, confidence, and risk awareness before committing to a timeline or sprint scope. |
| metadata | {"phase":"03-planning","inputs":["task-list","risk-register"],"outputs":["estimate-set"],"prerequisites":["pc-task-breakdown"],"quality_gate":"Each task has an estimate, confidence signal, and explicit assumption set suitable for sequencing or sprint commitment","roles":["tech-lead","developer"],"methodologies":["all"],"effort":"medium"} |
Estimate to expose uncertainty and trade-offs, not to pretend the future is certain.
Estimation converts a task list into a planning signal the team can actually use.
See context and anti-pattern notes.
I/O contract notes define required inputs and authority.
Pick one estimation approach for the planning horizon: hours, ideal days, story points, or size buckets. Keep it consistent within the same plan.
For each task, record:
If the estimate depends on an unresolved question, say so explicitly instead of guessing low.
Adjust estimates when risk, novelty, or coordination cost makes the base number misleading. Compare against similar recent work when available.
Package the estimates in a form sprint or milestone planning can consume directly. Distinguish between:
Produce only declared outputs at their documented quality boundary.
