菜单
Use when taking over an existing codebase that has no living document. Produces a factual record of what already exists.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Use at ship time to merge the spec into the living documentation, delete the staging spec and plan, and ask how to finish.
Use when all plan tasks are done and green to review, archive planning artifacts, and ask how to finish.
Use for standard or complex new work before coding or planning. Also handles vague goals — clarifies before designing.
Use at session start to learn how Praxis skills are invoked and why triage runs before every task.
Use when the goal is vague or vision-level and can't be defined well enough for design questions.
Use after design approval for milestone plans with executable acceptance.
基于 SOC 职业分类
| name | onboard |
| description | Use when taking over an existing codebase that has no living document. Produces a factual record of what already exists. |
Goal: read the codebase, produce living documentation. No code changes. No plans. No gap analysis.
README.md : project overview, what it is, who it's for, how to use it. Links to the technical specification.docs/tech-spec.md : main technical specification.docs/specs/*.md : created by splitting out details from the main spec if they are too bulky or complex. Reference by path from the main spec.technical specification is declarations only (no narrative), with facts only, no interpretation or plans.
docs/tech-spec.md uses the canonical format (field meanings: archive skill, "tech-spec format"):purpose / user / use-case / architecture / stack / entry /
contract / flow / invariant / constraint / convention
Omit milestone — onboard makes no plans. If details are bulky, split into docs/specs/ and link.
docs/tech-spec.md must contain: stack + at least one contract + at least one convention before done.
docs/tech-spec.md on disk → user continues with normal design → plan → tdd.