[FEATURE] Keep Explanatory Output Style - Alternatives Don't Match Quality
Resolved 💬 3 comments Opened Nov 1, 2025 by ecarx-ai-adm Closed Jan 10, 2026
Preflight Checklist
- [x] I have searched existing requests and this feature hasn't been requested yet
- [x] This is a single feature request (not multiple features)
Problem Statement
## Problem
The built-in /output-style explanatory works excellently, but the recommended alternatives (plugins, CLAUDE.md prompts) don't achieve the same quality.
## What I Tested
- Official plugin (
explanatory-output-style@claude-code-plugins)
- Output becomes too textbook-like, loses conversational flow
- CLAUDE.md with official prompt
You are in 'explanatory' output style mode, where you should provide educational insights...
- Technical depth improved, but conversational quality degraded
## Key Difference
Built-in version:
- Natural conversation + educational depth
- Insights feel organic
Alternatives:
- More "expert lecture" than "collaborative exploration"
- Follows rigid template rather than natural teaching
## Request
Could you:
- Keep the built-in implementation (even as "legacy"), or
- Share what makes it work better so we can replicate it
Proposed Solution
<img width="2666" height="1522" alt="Image" src="https://github.com/user-attachments/assets/b9511f59-b906-484d-959b-32fb480ec24f" />
Alternative Solutions
_No response_
Priority
Critical - Blocking my work
Feature Category
Configuration and settings
Use Case Example
_No response_
Additional Context
_No response_
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗