菜单
Build or update a Vercel-hosted static wiki for Git-tracked implementation plans, with left-sidebar accordion navigation from plan index to docs, task queues, and individual task pages; include validation, protected hosting, and review gates.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Run implementation work unattended/overnight with a review-driven PR loop. The agent picks one reviewable slice, owns its branch through an agnostic code review (CodeRabbit CLI or a fresh independent reviewer), may integrate agent-owned non-main branches after green gates, never merges to main, and reports a structured closeout. Replaces the retired kanban/dispatcher/polling model. Use when prompting an agent to work autonomously against a task queue or implementation plan.
Agent-owned CodeRabbit review loop for implementation branches. Use when reviewing or fixing a branch before closeout, with or without a hosted pull request.
Selects and applies the repo's engineering quality lens for implementation-plan Goals. Use when planning, reviewing, or starting a task and you need to choose TDD, diagnosis, architecture, DDD, DDIA, Release It, refactoring, or service-layer guidance.
Build or update a complete repo-native implementation plan from product intent, research, PRDs, specs, or conversations. Use when the user asks to create an implementation plan, roadmap, task queue, launch-ready overnight slices, plan index, decision log, or self-contained plan package for autonomous agents.
Interactively install or upgrade the Overnight autonomous orchestration system in a repository. Use when the user asks to set up Overnight, install the skill library, port overnight orchestration, configure AGENTS.md, wire plan preflight, choose plan roots, or make another repo ready for autonomous implementation-plan work.
Convert product conversations, PRDs, plans, or specs into repo-native implementation-plan artifacts and TASK_QUEUE.md rows instead of GitHub/Linear/external issue tracker tickets. Use when asked to create a PRD, break down a PRD/spec/plan into implementation work, create agent-ready tasks, adapt issue workflows to this repo, or maintain PRD-to-task traceability.
| name | implementation-plan-wiki |
| description | Build or update a Vercel-hosted static wiki for Git-tracked implementation plans, with left-sidebar accordion navigation from plan index to docs, task queues, and individual task pages; include validation, protected hosting, and review gates. |
Use this skill when turning implementation_plans/ into a hosted internal wiki
or updating the wiki generator for another project.
/ for all plans./plans/<plan>/ for plan overview./plans/<plan>/tasks/ for parsed queue rows./plans/<plan>/tasks/<task-id>/ for one task./plans/<plan>/docs/<doc-slug>/ for source docs.The shell is a dense, calm docs/wiki UI. Keep these conventions when editing it:
src/styles.css define a light token set on
:root, a dark set on :root[data-theme="dark"], and the same dark set under
@media (prefers-color-scheme: dark) scoped to :root:not([data-theme="light"])
so JS-disabled pages still follow the system theme. A tiny inline <head>
script (themeBootScript in build-site.mjs) applies the stored choice before
paint to avoid a flash; the .theme-toggle button in the topbar flips and
persists wiki-theme in localStorage via src/app.js.<= 860px the sidebar becomes a fixed off-canvas drawer toggled by
the .nav-toggle button and a .scrim backdrop (handled in src/app.js).
Keep .table-wrap { overflow-x: auto } and overflow-wrap: anywhere on body
text so content never overflows horizontally.--mono font for
task IDs, file/source paths, plan slugs, and status badges. Keep headings clear
but not oversized (h1 ~1.55rem)..nav-sub.active (accent left-border + tint). The
sidebar filter (#nav-filter) hides non-matching .nav-plan/.nav-sub items.Run the local checks before reporting completion:
npm run check --prefix implementation_plans/site
PLAN_PUBLIC_PLACEHOLDER=1 npm run build:public-placeholder --prefix implementation_plans/site
PLAN_PUBLIC_PLACEHOLDER=1 node implementation_plans/site/scripts/smoke-site.mjs
git diff --check
For non-trivial generator or plan changes:
.claude/skills/pr-review-loop/SKILL.md) when creating a
review branch or draft pull request (GitHub by default; other providers need
their configured review/check probe);This skill bundles a ready-to-use generator under template/. To stand up the
wiki in another repo:
Copy the template into the target repo's plans area:
mkdir -p <repo>/implementation_plans/site
cp -R .claude/skills/implementation-plan-wiki/template/. <repo>/implementation_plans/site/
cd <repo>/implementation_plans/site && npm install
Adjust the project-specific knobs in scripts/build-site.mjs
(plansRoot, excludedPlanDirs, planDocOrder, and the parseTaskQueue
column expectations) and set name in package.json. The template README
lists each knob.
Validate locally:
npm run check
PLAN_PUBLIC_PLACEHOLDER=1 npm run build:public-placeholder
Link and deploy with protection (see "Hosting" in the template README); keep
dist/ and .vercel/ out of Git.
Keep template/ in sync when you improve the live generator under
implementation_plans/site/ — the template is the reusable seed, not a fork.
Do not copy .vercel/, dist/, local env files, or deployment URLs between
projects.