菜单
Use when the user wants to review, polish, or share the generated Project Spine rationale file locally. Phrases like "show the project rationale", "send the client a project summary", "review rationale.md", or "make the client-facing overview safer".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when the user mentions AGENTS.md, CLAUDE.md, copilot-instructions, Cursor rules, project brief, context for coding agents, agency kickoff, onboarding a new project, or asks "how do I set up Project Spine". This is the orientation skill — reach for it FIRST when the user's intent involves Project Spine, then chain into a more specific active skill.
Use when the user asks about Project Spine hosted workspaces, team sync, shared workspace templates, invites, or commands such as `spine login`, `spine workspace`, `spine publish`, or `spine drift check --push`.
Use when the user wants to set up Project Spine for a new project — phrases like "new client project", "kickoff", "create AGENTS.md from scratch", "generate agent instructions for this repo", "set up project context". Runs `spine init` → edits brief → `spine compile` → reviews outputs. For stale files use project-spine-drift.
Use when the user mentions drift, says AGENTS.md / CLAUDE.md / copilot-instructions / Cursor rules are "stale" or "out of date", asks about CI catching docs drift, or says "check if my spine is still current". Runs `spine drift check`, interprets each drift category, and guides resolution. For initial setup use project-spine-kickoff.
Use when the user wants to apply a bundled, user-local, or project-local template to a new project, or save the current project as a reusable template. Phrases like "use our agency starter", "save this as a template for future clients", "apply the shared saas-marketing starter".
| name | project-spine-rationale |
| description | Use when the user wants to review, polish, or share the generated Project Spine rationale file locally. Phrases like "show the project rationale", "send the client a project summary", "review rationale.md", or "make the client-facing overview safer". |
Goal: help the user review .project-spine/exports/rationale.md before they share it through their normal channel. The public OSS CLI generates the file locally; it does not publish hosted rationale URLs.
.project-spine/exports/rationale.md exists. If not, switch to project-spine-kickoff.spine drift check first if the user mentions stale instructions or changed inputs.sed -n '1,220p' .project-spine/exports/rationale.md
Review the headings and content with the user. Do not paste the whole file into a public channel unless they explicitly ask.
Before the user shares the rationale, call out these sections:
If anything needs changing, edit the upstream brief.md or design inputs and rerun spine compile. Do not hand-edit rationale.md unless the user accepts that drift will be reported later.
If the file is safe, summarize it into a short client note:
Here is the Project Spine rationale generated from the current brief and repo.
It captures goals, audience, constraints, assumptions, risks, stack summary,
and the first scaffold direction. The generated files are local and versionable;
future drift is checked with `spine drift check`.
Do not tell users to run spine publish rationale, spine rationale list, or spine rationale revoke in the public OSS CLI. Those hosted commands exist in dormant source files but are intentionally not routed from spine --help.