菜单
One-shot wiki cleanup — runs lint, archives terminal items across all families, and rotates the log if overgrown, in sequence with user confirmation at each phase
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | wiki-tidy |
| description | One-shot wiki cleanup — runs lint, archives terminal items across all families, and rotates the log if overgrown, in sequence with user confirmation at each phase |
| category | wiki |
| model | claude-sonnet-4-6 |
| user-invocable | true |
Three-phase cleanup for a neglected wiki. Runs in order: lint → archive → rotate-log. Each phase summarises its findings and asks for confirmation before making changes. You can stop after any phase.
Run the full wiki-lint audit by following every step in /wiki-lint exactly as written:
Bash with find.lint entry to wiki/log.md.If the user types stop, end the skill here. Otherwise continue to Phase 2.
Run /wiki-archive as a cleanup sweep — it scans for any work items with terminal status that were not automatically moved to archive/ by their originating skill (uat-auto, bug-close, task-trash, etc.). In a healthy wiki this phase finds nothing; it exists as a safety net.
Scan all 6 families in sequence: tasks, uat, bugs, requirements, decisions, roadmaps.
For each family:
lifecycle.md to confirm the terminal statuses (do NOT hardcode).find wiki/work/<family>/ -maxdepth 1 -name "*.md" \
-not -name "lifecycle.md" -not -name "index.md" -not -name ".gitkeep" \
| xargs grep -lE "^status: (<terminal1>|<terminal2>)" 2>/dev/null
lifecycle.md. Files not returned are active — skip without reading.After scanning all 6 families, show a combined summary:
Archive candidates:
tasks — N items (TASK-012 done, TASK-019 trashed, …)
uat — N items (UAT-012 passed, …)
bugs — N items
requirements— N items
decisions — N items
roadmaps — N items
Total: N items across N families.
Ask: "Archive all, specific families (e.g. 'tasks uat'), or 'none' to skip? Type 'stop' to end wiki-tidy here."
For each confirmed family:
mv wiki/work/<family>/<file> wiki/work/<family>/archive/<file>id, title, status, and updated frontmatter.wiki/work/<family>/archive/index.md:
| [[ID]] | Title | final-status | YYYY-MM-DD |
index.md if it is still listed there.After all moves, append one archive entry to wiki/log.md:
## [YYYY-MM-DD] archive | wiki-tidy — N items archived across K families
Moved N terminal items: <comma-separated IDs>.
If the user types stop, end the skill here. Otherwise continue to Phase 3.
Run /wiki-rotate-log:
wiki/log.md and count the total number of lines.no, skip this phase; if stop, end the skill.date +%Y_%m_%d_%H%M%S and use log-<timestamp>.md (unique to the second — no collision handling needed).wiki/log.md → wiki/log-<timestamp>.md, create a fresh wiki/log.md with an archive-pointer header and a rotate entry as its first log line.After all three phases, print a one-paragraph summary:
Wiki tidy complete.
Lint: N issues found, M fixed.
Archive sweep: N stranded items moved (0 is healthy).
Log: rotated / not rotated (N entries).
stop at any phase prompt ends the skill immediately without proceeding further.Update the ai-sdd framework binary + skills to the latest release — an apply-on-confirm wrapper that runs `ai-sdd update --check`, surfaces the current-to-latest version transition, and (only on explicit confirmation) runs `ai-sdd update` and lands a standalone reseed commit. Agent-agnostic (claude-code or codex). Use when a teammate wants to update / upgrade ai-sdd, sees the update-available notice, or invokes `/ai-sdd-update`.
Stand up (or refresh) an ai-sdd factory for a repository so any coding agent — claude-code, codex, … — can drive it. Discovers the repo's conventions, scaffolds the .ai-sdd/ home, authors worker skills + schemas, compiles the deterministic gates, and wires provider-neutral skill surfacing (AGENTS.md + per-agent symlinks). Use when onboarding a repo to ai-sdd or re-bootstrapping after the codebase/conventions drift.
Drive a software-factory run by dispatching a sub-agent per worker — the deterministic `ai-sdd` engine plans (next), a fresh sub-agent does each worker's work via its skill, the engine gates and advances (submit), and each completed slice is committed. Agent-agnostic (claude-code or codex). Use when asked to run, drive, continue, or advance a factory run / pipeline / orchestration, or when the user mentions `ai-sdd next` / `ai-sdd submit`.
Print the diagram-driven ai-sdd workflow cheatsheet — the canonical command sequence (bootstrap → plan → run, validate/next/submit/status) that travels with the binary. Use when a user forgets which command comes next, asks "how do I drive a run / what's the workflow", or needs the command reference without leaving the repo.
Turn a complete PROGRAM brief into a runnable master plan — a decision-closed program requirements doc and a master orchestration graph whose nodes are whole sub-features (kind:pipeline) sequenced by milestone validation gates with owners. The program tier above ai-sdd-plan. Requires a real program brief (refuses a one-liner) and human approval of the program requirements draft before emitting the graph. Use when planning a multi-feature, multi-person project in a bootstrapped repo (run ai-sdd-bootstrap first); each sub-feature is then planned with ai-sdd-plan. Re-run on an existing program to amend it in place (create-vs-amend is auto-detected from disk): append sub-features/milestones and rewire pending nodes; a started node (completed or in-flight) is immutable and corrected forward with a downstream `<node>-revert` node.
Turn a complete feature brief into a runnable plan for a bootstrapped repo — a decision-closed requirements doc and an orchestration graph (slices + depends_on) the engine executes. Requires a real brief (refuses a bare one-liner — asks for one) and human approval of the requirements draft before generating slices. The planning layer between an idea and ai-sdd-run. Use when starting a new feature in a repo that already has a .ai-sdd/ (run ai-sdd-bootstrap first). Re-run on an existing feature to amend it in place (create-vs-amend is auto-detected from disk): append slices and rewire pending ones; a started slice (completed or in-flight) is immutable and corrected forward with a downstream `<slice>-revert` slice.