菜单
Configures this repository for the engineering skills by writing .claude/engineering.local.md — where specs, plans, and ADRs are saved, if at all — and excluding it from git locally. Run once per repository before relying on doc-saving skills.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
A relentless one-question-at-a-time interview that sharpens a plan, decision, or idea until shared understanding is reached — not limited to software. Use when the user wants requirements or a decision clarified before acting, wants to stress-test their thinking, or asks to "grill me", "詰めて", "brainstorm this".
Executes an implementation plan or agreed work by orchestrating fresh subagents — one implementer per task, a reviewer between tasks — while the main model plans, briefs, and evaluates without writing code itself. Use when the user asks to "implement the plan", "start implementation", "実装して", or hands over a plan or spec to execute.
A feedback-loop-first discipline for diagnosing hard bugs and performance regressions. Use when the user reports something broken, throwing, failing, flaky, or slow, or asks to "diagnose", "debug this", "原因を調べて".
Builds a clearly-marked throwaway prototype to answer a design question before committing to an implementation. Use when the user wants to sanity-check whether logic or a state model feels right, explore what a UI should look like, or asks to "prototype this", "試作して".
Creates an Architecture Decision Record for a decision that is hard to reverse, surprising without context, and the result of a real trade-off. Use when such a decision has just been made, or the user asks to "record this decision", "ADRにして", or mentions decision records.
Reviews the diff since a fixed point along two axes run as parallel subagents — Spec (does the change match what was asked?) and Standards (repo conventions plus a code-smell baseline) — and reports them side by side. Use when the user asks to review a branch, work-in-progress changes, a diff, or "review since X".
| name | setup-engineering |
| description | Configures this repository for the engineering skills by writing .claude/engineering.local.md — where specs, plans, and ADRs are saved, if at all — and excluding it from git locally. Run once per repository before relying on doc-saving skills. |
| disable-model-invocation | true |
Scaffold .claude/engineering.local.md, the per-repo config that write-spec, write-plan, and record-adr read to know where — if anywhere — to save their output.
This is a prompt-driven skill, not a deterministic script. Explore, present what you found, confirm with the user, then write.
Look at the repo before asking anything:
docs/ layout — existing subdirectories for specs, plans, or design docsdocs/adr/, docs/decisions/, or similar, and whether entries are already numberedSPEC.md, PLAN.md, or a docs folder with dated filespnpm-workspace.yaml, a workspaces field in package.json, or populated packages/*/docs — these suggest per-package paths might fit better than repo-root ones.claude/engineering.local.md already exists — if so, this run is a redo, not a first setupSummarize what's present and missing, then propose one value per key, leading with the recommendation so the user can accept in a word. If .claude/engineering.local.md already exists, present its current values as the default for each key, and fall back to fresh exploration only to fill in whatever is missing.
specs: — where spec documents go (an existing specs-shaped directory if found, otherwise docs/specs, or none to skip saving)plans: — where implementation plans go (same logic, e.g. docs/plans)adr: — where ADRs go (an existing ADR directory if found, otherwise docs/adr)Ask about project notes only if exploration surfaced something worth recording (a non-obvious doc convention, a naming rule); otherwise leave the notes body empty and mention it can be filled in later.
Show the confirmed values and let the user edit before writing.
Write .claude/engineering.local.md from references/config-template.md, filling in the three keys and any notes.
Then check .git/info/exclude for a .claude/engineering.local.md line with grep, appending it only if absent. Leave .gitignore, CLAUDE.md, and AGENTS.md untouched — this file is local-only config, not a project convention worth sharing.
Tell the user the file can be edited directly going forward — re-running this skill is only needed to start over.