メニュー
Configure a repo for rail skills — all docs under docs/monorail/ (work tracker + domain). Run once per repo before other rail engineering skills.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/guangzan/monorail --skill rail-setupコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
Implement docs/monorail tasks serially in one session — drive rail-tdd at agreed seams, then commit.
Ask which rail skill or flow fits. Router over the rail pack.
Align on a plan or design — light grilling with domain docs by default; map mode for foggy multi-session efforts. Light mode writes docs/monorail/<slug>/align.md then auto-continues the planning chain (spec → slice).
| name | rail-setup |
| description | Configure a repo for rail skills — all docs under docs/monorail/ (work tracker + domain). Run once per repo before other rail engineering skills. |
| disable-model-invocation | true |
Scaffold per-repo configuration that rail engineering skills assume:
docs/monorail/ — work tracker, glossary, ADRs, and convention files (no remote tracker; no scatter to repo root / docs/agents/ / docs/adr/)docs/monorail/CONTEXT.md + docs/monorail/adr/This is prompt-driven, not a deterministic script. Explore, present, then write — never pause to ask the user to confirm the plan.
Read what exists; do not assume:
AGENTS.md / CLAUDE.md — either present? Already has ## Agent skills?docs/monorail/ — already in use? work-tracker.md / domain.md / CONTEXT.md / adr/?CONTEXT.md / CONTEXT-MAP.md, docs/adr/, docs/agents/pnpm-workspace.yaml, package workspaces, populated packages/*)Summarise present vs missing. Then:
Doc root — state that rail keeps all docs under docs/monorail/ only. Show templates at templates/work-tracker.md and templates/domain.md (relative to this skill). Use the default root (docs/monorail/); adjust path wording only if the user explicitly asks for a non-default root. If they insist on a remote tracker, refuse for rail skills and stop — rail v1 is local-only. If legacy paths exist, tell the user to move them under docs/monorail/ manually (do not rewrite their content in this skill).
Domain docs — default single-context (docs/monorail/CONTEXT.md + docs/monorail/adr/). Offer multi-context only when exploration found monorepo signals (docs/monorail/CONTEXT-MAP.md; per-context paths still under docs/monorail/).
Write immediately after presenting — no confirmation, no waiting for edits. Show each draft as you go, then report what was written. The pieces to write:
## Agent skills block for CLAUDE.md or AGENTS.mddocs/monorail/work-tracker.md (from template, path adjusted if needed)docs/monorail/domain.md (from template)Pick file for Agent skills block:
CLAUDE.md exists, edit itAGENTS.md exists, edit itAgent skills block (adapt if work root changed) — include these bullets verbatim in the target file:
## Agent skillsdocs/monorail/.docs/monorail/work-tracker.mddocs/monorail/domain.md/rail-setup again only if these conventions change. Prefer /rail to see the main flow.Write docs/monorail/work-tracker.md and docs/monorail/domain.md from the templates in this skill folder. Create docs/monorail/ if needed. Do not create CONTEXT.md / adr/ until /rail-align needs them.
Done when both convention files exist under docs/monorail/, the Agent skills block is present, and you told the user they can start with /rail-align or /rail.