Completion reports

Success Output

User-runnable refresh rendering. The reports below print a ce-compound-refresh invocation for the user to copy. Default to /ce-compound-refresh <scope>; use $ce-compound-refresh <scope> only when the active host is Codex or explicitly documents dollar-prefixed skill invocation. Render only the invocation as inline code and output one form only.

Non-interactive mode

Emit a structured terminal report as the last thing this skill writes. No "What's next?" question, no blocking prompt. The report ends this skill, not the turn. When a caller invoked this skill, its next step follows the report in the same session; otherwise end the turn. End with Documentation complete as the terminal signal so callers can detect completion.

For depth:lightweight, use this lower-overhead report after the Lightweight Mode workflow:

✓ Documentation complete (non-interactive lightweight mode)

File: <root>/solutions/<category>/<filename>.md  (created | updated)
Track: <bug | knowledge>
Category: <category>
Grounding: <mechanical check clean | N flags adjudicated>
Discoverability: <no gap | gap noted — instruction-file tip emitted | not applicable — no active project instructions>
CONCEPTS.md: <not present | scanned, no qualifying terms | updated — N added, N refined, N folded, N scrubbed>
CONCEPTS.md discoverability: <not checked — CONCEPTS.md unchanged | no gap | gap noted — instruction-file tip emitted | not applicable — no active project instructions>
Refresh recommendation: <none | scope hint for /ce-compound-refresh>

Documentation complete

For depth:full or backward-compatible non-interactive calls with no depth token, use the Full report:

✓ Documentation complete (non-interactive mode)

File: <root>/solutions/<category>/<filename>.md  (created | updated)
Track: <bug | knowledge>
Category: <category>
Overlap: <none | low | moderate — see <path> | high — existing doc updated>
Grounding: <clean | N flags adjudicated (X fixed, Y annotated, Z confirmed) | N claims softened or corrected | degraded — merge-state claims unverified offline>
Instruction-file edit: <none needed | gap noted, not applied>
CONCEPTS.md: <scanned, no qualifying terms | created with N entries (M seeded from the learning's area) | updated — N added, N refined, N folded, N scrubbed>
Refresh recommendation: <none | scope hint for /ce-compound-refresh>

Documentation complete

When no doc was written (e.g., non-interactive invoked on a session where the problem is not yet solved), emit a structured failure instead and end with Documentation skipped so callers can distinguish success from no-op:

✗ Documentation skipped (non-interactive mode)

Reason: <one-sentence explanation — e.g., "no solved problem detected in
conversation history" or "solution not yet verified">

Documentation skipped

Interactive mode

✓ Documentation complete

Ran Full mode.
Auto memory: 2 relevant entries used as supplementary evidence

Research Results:
  ✓ Classified: performance_issue in background_job (component from corpus), category: performance-issues/
  ✓ Drafted: 3 code fixes, prevention strategies
  ✓ Related Docs Finder: 2 related issues
  ✓ Session History: 3 prior sessions on same branch, 2 failed approaches surfaced

Grounding Validation:
  ✓ Mechanical check: 14 paths, 2 SHAs, 3 links checked — 1 flag annotated as historical
  ✓ Semantic validator: 9 claims verified, 1 merge-state claim softened to pending

Specialized Agent Reviews (Auto-Triggered):
  ✓ performance-oracle: Validated query optimization approach
  ✓ Code simplification review: Code examples are appropriately minimal

Files written:
- <root>/solutions/performance-issues/n-plus-one-brief-generation.md (created)
- CONCEPTS.md (created with 3 entries: BriefSystem, EmailQueue, Brief Status)

This documentation will be searchable for future reference when similar
issues occur in the Email Processing or Brief System modules.

Refresh recommendation: none

Files written: lists the destination the assembly step settled on. That is a pack rule's path (<pack dir>/<file>.md) when the user routed the capture into a writable pack, and the <root>/solutions/ path otherwise.

**The summary is the last thing this skill writes. When a caller invoked this skill, its next step follows the summary in the same session; otherwise end the turn. ce-compound does not present a "What's next?" menu.** The doc is written and any cross-references the workflow found are already in it. Cross-doc maintenance (fixing references in other docs, consolidation) is left to ce-compound-refresh, the skill designed for it, through the Refresh recommendation line above. It is not applied here, because that would edit tracked docs beyond the one deliverable. If the user wants to view the file or take a follow-up action, they will ask. (Interactive mode only.)

Alternate interactive output (when updating an existing doc due to high overlap): in non-interactive mode, this case is communicated via the Overlap: high — existing doc updated line of the non-interactive terminal report above, not as a separate output block.

✓ Documentation updated (existing doc refreshed with current context)

Overlap detected: <root>/solutions/performance-issues/n-plus-one-queries.md
  Matched dimensions: problem statement, root cause, solution, referenced files
  Action: Updated existing doc with fresher code examples and prevention tips

File updated:
- <root>/solutions/performance-issues/n-plus-one-queries.md (added last_updated: 2026-03-24)

Common Mistakes to Avoid