메뉴
Plan a feature, bugfix, refactor, or improvement with wiki research first. Searches project and main cross-project wiki context, synthesizes Past Knowledge, then delegates to Compound Engineering planning when available or writes a standalone plan outline.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Upgrade an existing project's managed llm-wiki structure without rerunning broad wiki bootstrap. Use when a user asks to migrate, update, or upgrade project-local .llm-wiki scripts, hooks, or changelog structure after installing a newer llm-wiki release.
Bootstrap an LLM-maintained wiki for the current project. Use when a user asks to create, initialize, or refresh a project wiki, LLM wiki, QMD wiki, or codebase knowledge base for Claude Code, Codex, or Pi.
Check whether llm-wiki is current, detect newer marketplace or Pi package versions, and suggest or run the right update command for Claude Code, Codex, or Pi. Use when the user asks about llm-wiki version, plugin/package updates, marketplace refresh, upgrade instructions, project context setup, or whether a new llm-wiki release is available.
Check llm-wiki install status, version freshness, update commands, and project wiki automation from Pi. Use when a Pi user asks about llm-wiki version, package updates, refresh ownership, context setup, or whether a new llm-wiki release is available.
Upgrade an existing project's managed llm-wiki structure from Pi without rerunning broad bootstrap.
Bootstrap an LLM-maintained wiki for the current project from Pi. Use when a Pi user asks to create, initialize, refresh, or configure a project wiki, LLM wiki, QMD wiki, or codebase knowledge base.
| name | wiki-plan |
| description | Plan a feature, bugfix, refactor, or improvement with wiki research first. Searches project and main cross-project wiki context, synthesizes Past Knowledge, then delegates to Compound Engineering planning when available or writes a standalone plan outline. |
Plan with wiki knowledge first. Use this when the user asks to plan work and wants existing project knowledge, prior decisions, or cross-project patterns included.
Argument: feature description, bug report, refactor, or improvement idea.
<feature_description> $ARGUMENTS </feature_description>
If the feature description is empty, ask the user what they want to plan and wait for the answer.
Use the research skill on the feature description before any other planning research.
The output must include a Past Knowledge section with:
If no wiki exists, continue with an explicit note:
### Past Knowledge
No project wiki was found. Consider running `bootstrap` after this plan. Proceeding with normal planning.
If Compound Engineering planning is installed, invoke it with the original feature description plus the Past Knowledge section.
Common Codex installed form:
$compound-engineering:ce-plan
Common Claude/Codex skill name:
compound-engineering:ce-plan
Use the platform's available skill invocation mechanism. Do not pretend delegation happened if the skill is unavailable.
If Compound Engineering planning is unavailable, create a concise standalone implementation plan with:
Keep the plan grounded in source files and wiki pages actually read.
qmd CLI or rg.plan command. This skill is wiki-plan.