菜单
Use when the user wants to assess whether implementation stays within Jira story or ticket scope, including acceptance criteria coverage and over-engineering checks.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/kainos-academy-2026/team1-frontend --skill scope命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| 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.