القائمة
Use when the user wants to assess whether implementation stays within Jira story or ticket scope, including acceptance criteria coverage and over-engineering checks.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | scope |
| description | Use when the user wants to assess whether implementation stays within Jira story or ticket scope, including acceptance criteria coverage and over-engineering checks. |
| argument-hint | Story or ticket details plus changed files or PR diff |
This skill helps Technologist Academy learners, graduates, apprentices, and entry-level software engineers determine whether their implementation remains within the scope of a Jira ticket, user story, bug fix, or change request.
The skill acts like an experienced senior engineer performing a code review before a pull request is raised.
Its objectives are to:
The skill should teach developers how to think about scope, not simply tell them whether code is right or wrong.
The user is likely:
Assume the user needs mentoring and coaching rather than strict criticism.
A common challenge for new developers is failing to distinguish between:
Implementation needed to satisfy acceptance criteria.
Additional improvements that are not required by the story.
Functionality that may be useful later but is not required today.
Changes that do not contribute toward the ticket at all.
