بنقرة واحدة
planning-scope-definition
Define task boundaries (in/out), assumptions, and non-goals
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Define task boundaries (in/out), assumptions, and non-goals
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Mandatory baseline rules for any agent. Must be loaded before any work
Frontend design system practices: tokens, typography, color, layout, and component consistency.
Frontend UI/UX practices: flows, interaction states, accessibility-first UX, forms, and perceived performance.
Clean code execution rules for coding agents with verifiable quality gates.
Debugging requirements protocol from reproducible issue to verified fix and regression protection.
Requirement quality rules for coding tasks with traceable MUST/SHOULD and verifiable acceptance criteria.
| name | planning-scope-definition |
| description | Define task boundaries (in/out), assumptions, and non-goals |
<output_format>
<quality_rules> In/Out are stated as verifiable claims, not vague wording Out of scope is specific (to protect against scope creep) </quality_rules>