npx skills add ...
npx skills add everyinc/compound-writing --skill cw-outline
Organize interview material into a detailed structure using the 10%/30% framework. Invoke with /cw-outline or after completing an interview.
npx skills add everyinc/compound-writing --skill cw-outline
Organize material into a structure the writer approves before drafting. Goal: no surprises at the draft stage.
| Element | Description |
|---|---|
| Logical architecture | The overall structure makes sense for the argument |
| Clear hierarchy | Reader can tell what's a main point vs. supporting point |
| Flow | Ideas connect within sections and between sections |
| Gaps visible | Open loops and questions are surfaced, not hidden |
Organize material logically; writer reshapes from there. Don't impose templates or force a particular form. Match the outline depth to the piece complexity.
Beats describe what happens in the piece, not what rhetorical function must happen there. A beat may be a scene, claim, example, question, piece of evidence, objection, explanation, turn, or something else the material requires. Do not assign beats a predetermined sequence such as setup → complication → implication, and do not pad an outline to produce a fixed number of beats.
A guideline, not a requirement. Use your judgment about how much structure this piece needs.
What it contains:
When it's enough: Short pieces, simple arguments, experienced writers who just need a skeleton.
When to go deeper: Complex arguments, lots of evidence, writer wants more detail before drafting.
A 30% outline contains the complete shape of the piece in compressed form. It identifies the major sections, the point of each section, the material it will contain, and how the sections connect. It is not 30% of the prose.
When to use: Longer pieces, complex topics, or when the writer wants to see everything before drafting.
Use this as the standard shape, adapting the number of sections and beats to the material.
The labels are structural prompts, not quotas or a hidden narrative formula:
These are questions, not gates:
Surface issues constructively. Don't block progress—flag concerns and let the writer decide.
Track questions and gaps that emerge:
Open loops don't block progress. They're carried forward for the writer to resolve during drafting or address later. Some will resolve naturally; others need explicit attention.
Present the outline → get feedback → iterate. Keep it conversational:
The outline is ready when the writer feels ready to draft. This might be:
Don't gatekeep. If the writer says "let's draft," move to draft.
When invoked as part of a larger workflow, this skill returns:
[Skill-specific lessons will be added here as they're captured]
## Open Loops
- [ ] Need example for section 3
- [ ] Counterargument to address?
- [ ] Ending still unclear