菜单
Gives a fresh agent a plan, audits it for comprehension gaps, and verifies technical assumptions against the codebase before implementation begins. Spawns a single sub-agent to perform both checks and presents the findings.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/jackfranklin/dotfiles --skill onboard-plan命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Collaboratively discuss designs, evaluate trade-offs, and explore alternative implementation approaches. Starts from the simplest viable option and explores justified alternatives without fixed personas.
Implements an approved code-change plan safely. Use when beginning a feature, bug fix, or refactor that requires source changes, tests, a dedicated branch, small logical commits, and a GitHub pull request when applicable.
Write a right-sized, no-placeholder implementation plan as a series of focused tasks, with exact file paths, implementation details, proportionate test steps, and commit instructions. Performs a pre-planning preflight investigation and Ponytail decision ladder checks before drafting the plan. Reviews the plan with the user task by task before storing an explicitly approved plan on the relevant GitHub issue.
基于 SOC 职业分类
正在显示 SKILL.md
| disable-model-invocation | true |
| name | onboard-plan |
| description | Gives a fresh agent a plan, audits it for comprehension gaps, and verifies technical assumptions against the codebase before implementation begins. Spawns a single sub-agent to perform both checks and presents the findings. |
Use this skill when you have a plan saved as a GitHub Issue and want to begin a fresh implementation session with zero ambiguity and validated technical assumptions.
The skill argument may be:
gh issue view <number> --json title,body.gh issue list --search "[PLAN] <description>" --state open --json number,title
and pick the best match by title similarity. If more than one is plausible,
ask the user to choose before proceeding.Read the full issue body. Do not summarise or paraphrase it at this stage.
Spawn a single research or self subagent to audit the plan. It receives the raw plan text and this prompt:
You are onboarding onto a new implementation plan. Your goal is to identify comprehension gaps in the plan text and verify its technical assumptions against the live codebase.
PLAN:
{PLAN_CONTENT}
Perform the following tasks:
1. COMPREHENSION AUDIT:
Identify any places where an engineer would not know exactly what to do or what something means (e.g. undefined terms, ambiguous steps, sequencing issues).
Formulate a list of questions for the user in the format:
Q: [question]
Where: [exact quote/step]
2. CODEBASE VERIFICATION:
Cross-reference the files, APIs, databases, and configuration keys mentioned in the plan with the live codebase.
Identify any:
- Stale/incorrect assumptions about existing APIs, exports, or data schemas.
- Mismatches in configuration or file layouts.
- Hidden dependencies/prerequisites omitted from the plan.
Constraints:
- Do not suggest or make changes to the codebase.
- Rely only on live codebase verification (do not guess).
- Focus only on technical blocking issues.
Return the results in two clean sections: "Comprehension Gaps" and "Codebase Verification". No preamble, no summary.
Display the results returned by the subagent. Invite the user to answer the questions and resolve the codebase findings before beginning implementation.