用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/guangzan/monorail --skill rail命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Implement docs/monorail tasks serially in one session — drive rail-tdd at agreed seams, then commit.
Configure a repo for rail skills — all docs under docs/monorail/ (work tracker + domain). Run once per repo before other rail engineering skills.
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).
正在显示 SKILL.md
| name | rail |
| description | Ask which rail skill or flow fits. Router over the rail pack. |
| disable-model-invocation | true |
A flow is a path through skills. Most work follows the main chain.
/rail-setup — once per repo (all rail docs under docs/monorail/)/rail-align — light grilling → writes align.md; map mode if foggy/multi-session/rail-spec — write docs/monorail/<feature>/spec.md from align.md and/or a cleared map (refuses empty context)/rail-slice — write tasks/NN-*.md with blockers/rail-build — user-triggered; runs frontier tasks serially in one session (fresh implementer sub-agent per non-trivial task, trivial tasks inline); drives /rail-tdd, then marks done. Concurrent builds require separate git worktrees (see rail-build)align → spec → slice is one planning chain. When a stage finishes successfully in this session, continue the next stage in the same session by reading and following that skill's SKILL.md — do not stop and ask the user to type the next /rail-*.
align.md → continue /rail-spec → continue /rail-slice/rail-spec → continue /rail-slice/rail-spec auto-continues to /rail-slice; /rail-slice ends the planning chain (suggest /rail-build only)Do not auto-continue into /rail-build — build stays user-triggered: the planning chain ends at slice so you can review the task list before implementation starts. Once a build starts, it runs tasks serially in the same session — finishing one task continues to the next frontier task with no fresh session and no context-clearing between tasks (non-trivial tasks are isolated in fresh implementer sub-agents). Builds ask nothing: defaults are run to queue-clear with one commit per task; the user states any deviation (review pause, no-commit, narrower run) in their command. If the run's context degrades, /rail-pass or a fresh sub-agent resumes it. To run several builds at once, set up one git worktree per task first — more sessions on the same cwd are not parallel-safe.
Stop auto-continue when: the user asked to stop after this stage; context is near limits (use /rail-pass); or an adequacy / map / fail-closed gate says stop.
If the window breaks mid-chain, durable align.md / map / spec.md still feed the next skill when the user resumes.
Handoffs (auto-continue or suggest) use the next rail skill by exact name (/rail-align, /rail-spec, /rail-slice, /rail-build, …). Do not substitute lookalike skills from other packs (e.g. /to-spec for /rail-spec, /to-tickets / /to-issues for /rail-slice) even if those are installed in the same agent.
/rail-grill/rail-pass/rail-debug/rail-review (opt-in; not part of build)/rail-tdd — red-green-refactor (also used inside build)In /rail-align map mode, decision tickets may be Type: decision | research | prototype (see rail-align/map-mode.md). There is no /rail-research or /rail-prototype skill.
triage, standalone wayfinder, architecture-improve tours — use other packs or wait for a later rail version.