Commands

Refactor

Document restructuring

Refactor applies the pyramid principle, consistent heading hierarchy, focused paragraphs, and smooth transitions — changing structure without changing substance. Same content, dramatically better flow.

How it works

Same substance,
dramatically better structure

Open a document and run /refactor. It restructures for clarity: conclusion first, logical flow, consistent headings, one idea per paragraph, smooth transitions. All content preserved.

Pyramid Principle

Conclusion first. Supporting arguments below. Detail last. Every reader gets the answer immediately, then can go deeper if they choose.

Before: 3 pages of context → conclusion. After: Conclusion → context.

Consistent Hierarchy

Heading levels corrected. Paragraph focus enforced — one idea each. Transition sentences added between sections. Scannable structure throughout.

Fixed: H1 → H3 → H2 (broken hierarchy) → H1 → H2 → H3 (correct)

Noise Removal

Redundancy eliminated. Filler words cut. Passive voice converted to active. Every word earns its place. Content preserved, noise gone.

Before: 4,200 words. After: 2,800 words. Zero content lost.

Complete Output

Returns the entire document — not a list of suggestions. The restructured document is ready to replace the original. One command, done.

Complete restructured document created as refactored-{filename}.md

Structure, not substance

Not "let me rewrite this for you."
Every fact preserved. Only the structure changes.

Original Document
Conclusion buried on page 5
Three paragraphs that say the same thing
Heading levels inconsistent
1,400 filler words diluting the message
After /refactor
Conclusion in the first paragraph (pyramid principle)
Each paragraph makes exactly one point
Clean H1 → H2 → H3 hierarchy throughout
40% shorter — same content, zero filler

Any document worth polishing

Good content. Better structure.

When the ideas are right but the document doesn't flow.

White Papers

Technical depth restructured for executive readability

Proposals

Persuasive flow with conclusion first, evidence below

Internal Memos

Cut the preamble — action items and decisions up front

Documentation

Consistent hierarchy, scannable sections, progressive detail

Legal Briefs

Argument flow restructured for maximum persuasive impact

Research Reports

Findings-first structure with methodology as supporting detail

Ready to refactor?

Open a file in the Workspace and run /refactor from the Conductor.

Get AskQP