메뉴
Use when checking RagKit index health — doc and chunk counts, backend resolution, staleness and drift between knowledge-base/ and index. Trigger /ragkit:status. Rebuilding after drift uses ragkit:embed.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | status |
| description | Use when checking RagKit index health — doc and chunk counts, backend resolution, staleness and drift between knowledge-base/ and index. Trigger /ragkit:status. Rebuilding after drift uses ragkit:embed. |
脚本在本插件的 scripts/ 目录（本 skill 目录的上两级）；用本 skill 的 base directory 把下面的相对路径拼成绝对路径执行。
sh ../../scripts/run.sh ../../scripts/ragkit.py \
status --kb <项目根>/knowledge-base --json
解读：drift.missing_from_index 非空或 index_stale: true → 建议重跑 embed；backend_resolved: none → 原样转述固定提示块。
Use when running a spec's execution tail — presents the 执行方式 selector, dispatches the chosen engine (task-swarm / superpowers / specode-native TDD), then runs acceptance and the distill prompt. Trigger /specode:execute <slug> manually at any time once tasks.md exists, or invoked by name (specode:execute) via the Skill tool by the spec / continue skills.
Use when running specode's requirements phase — project analysis + code location + clarification, then writing requirements.md. Produces <specsRoot>/<slug>/requirements.md (with the project_root frontmatter contract) plus the location pointers handed to the design phase. Invoked by name (specode:intake) via the Skill tool by the specode orchestration SKILL; not a user-triggered command.
Use when creating a new spec-driven workflow — the /specode:spec entry that walks requirements → design → tasks → 执行方式 → execute → acceptance, autonomously calling superpowers skills for the heavy lifting with a first-class specode-native fallback, and filing 4 fixed artifacts (requirements.md / design.md / tasks.md / implementation-log.md) under the user document directory. Trigger /specode:spec <request>, or 进入 spec 模式 with a new requirement.
Use when resuming an existing spec by slug — the /specode:continue entry that reads the fixed docs, reports a progress brief (inferred phase + checkbox progress), then stops and waits for the user; it never auto-resumes. Trigger /specode:continue <slug>.
Use when distilling a finished specode spec into atomic, locate-oriented markdown knowledge points — writes cases/ + navigation/ + MEMORY.md into the project's own <project_root>/knowledge-base/ (md-only, no auto-injection), optionally copied to an Obsidian vault. Trigger ONLY /specode:distill <slug>, never auto-run by the main specode flow.
Use when listing all specs under the specs root — the /specode:list entry that shows every spec slug with its inferred phase, for looking up slugs or an overview; it does not resume. Trigger /specode:list.