القائمة
Capture what happened, what worked, what failed, and what should change after a sprint, milestone, incident, or release. Use after meaningful outcomes.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Design or tune a combat loop including enemy roles, feedback, pacing, damage model, and skill expression. Use for combat-heavy slices and balance passes.
Audit or frame engine-specific project setup, folder conventions, packages/plugins, and build assumptions. Use for Godot, Unity, or Unreal setup and repo structure decisions.
Specify a single player mechanic with verbs, inputs, feedback, tuning surfaces, edge cases, and testability. Use for movement, abilities, interactions, or systemic verbs.
Design or implement one UI flow with screen states, transitions, copy needs, and validation. Use for menus, HUD flows, settings, or onboarding screens.
Audit a feature or build for control, readability, timing, color, subtitle, and assist-option risks. Use during feature review or release prep.
Write or revise an ADR for technical decisions with significant maintenance, performance, or pipeline impact. Do not use for tiny local refactors.
| name | postmortem |
| description | Capture what happened, what worked, what failed, and what should change after a sprint, milestone, incident, or release. Use after meaningful outcomes. |
Capture what happened, what worked, what failed, and what should change after a sprint, milestone, incident, or release. Use after meaningful outcomes.
producertechnical_directorcommunity_managerstudio/docs/templates/postmortem.mdstudio/docs/active/decision-log.md