メニュー
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コマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？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.