john/claude-engineering-plugin
1
0
Fork 0
Code Issues Pull Requests Actions 3 Packages Projects Releases Wiki Activity

fix(skills): improve ce:compound-refresh interaction and auto-archive behavior

Browse Source 
- Use platform-agnostic interactive question tool phrasing with examples
  for Claude Code and Codex instead of hardcoding AskUserQuestion
- Fix contradiction between Phase 2 auto-archive criteria and Phase 3
  always-ask-before-archive rule so unambiguous archives proceed without
  unnecessary user prompts
This commit is contained in:
Trevin Chow
2026-03-13 12:07:16 -07:00
parent bd3088a851
commit 0dff9431ce
1 changed files with 3 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
plugins/compound-engineering/skills/ce-compound-refresh/SKILL.md
View File

@@ -13,7 +13,7 @@ Maintain the quality of `docs/solutions/` over time. This workflow reviews exist
Follow the same interaction style as `ce:brainstorm`:
- Ask questions **one at a time**
- Ask questions **one at a time** — use the platform's interactive question tool (e.g. `AskUserQuestion` in Claude Code, `request_user_input` in Codex) and **stop to wait for the answer** before continuing
- Prefer **multiple choice** when natural options exist
- Start with **scope and intent**, then narrow only when needed
- Do **not** ask the user to make decisions before you have evidence
@@ -234,16 +234,14 @@ If "archive" feels too strong but the pattern should no longer be elevated, redu
Most Updates should be applied directly without asking. Only ask the user when:
- The right action is genuinely ambiguous (Update vs Replace vs Archive)
- You are about to Archive a document
- You are about to Archive a document **and** the evidence is not unambiguous (see auto-archive criteria in Phase 2). When auto-archive criteria are met, proceed without asking.
- You are about to create a successor via `ce:compound`
Do **not** ask questions about whether code changes were intentional, whether the user wants to fix bugs in the code, or other concerns outside doc maintenance. Stay in your lane — doc accuracy.
### Question Style
Use the **AskUserQuestion tool** when available.
If the environment does not support interactive prompts, present numbered options in plain text and wait for the user's response before proceeding.
Always present choices using the platform's interactive question tool (e.g. `AskUserQuestion` in Claude Code, `request_user_input` in Codex). If the environment has no interactive prompt tool, present numbered options in plain text and wait for the user's response before proceeding.
Question rules: