---
name: express-workflow
description: Turn existing notes, research, and reusable drafts into a requested article, presentation, report, or other deliverable.
---

# Express Workflow — From Notes to Output

Transform captured, organized, and distilled knowledge into tangible creative output.
This skill operationalizes the Express stage of the CODE framework by assembling
Intermediate Packets into finished deliverables.

## When to Use

- The user has notes, research, or captures and wants to produce output
- The user is facing a blank page and needs structure
- The user feels overwhelmed by project scope
- The user wants to reuse past work in a new context

## Process Overview

The Express workflow has four phases. Not every session uses all four -- enter at
whichever phase matches the user's current state.

### Phase 1: Gather Intermediate Packets

Intermediate Packets (IPs) are the discrete, reusable building blocks of creative work.

**The 5 types of IPs:**
1. **Distilled notes** -- progressively summarized notes from the Second Brain
2. **Outtakes** -- material cut from past projects
3. **Work-in-process** -- drafts, outlines, agendas in progress
4. **Final deliverables** -- completed outputs from past projects
5. **Documents created by others** -- research, templates, frameworks

**Gathering process:**

Ask the user:
> "What output are you trying to create? (article, presentation, report, email, proposal, etc.)
> And what do you already have -- notes, outlines, research, past drafts?"

Then help search for relevant IPs:
- Search the user's PARA folders for related notes and past project materials
- Check Archives for completed projects on similar topics
- Check Resources for reference material
- Ask: "Have you written anything related to this before, even partially?"

### Phase 2: Build an Archipelago of Ideas

Transform scattered IPs into a structured outline.

**Step 1 — Diverge:** Collect all relevant ideas, quotes, data points, and notes.
List them without organizing.

**Step 2 — Arrange:** Sequence the collected elements into a logical outline.
Group related items. Identify the narrative arc or argument structure.

> "Here are your gathered materials arranged into a sequence. Each item is a
> 'stepping stone' -- the blank page problem is solved because the raw material
> is already in front of you."

**Step 3 — Identify gaps:** Flag where the outline needs:
- A missing transition between sections
- Supporting evidence or examples
- An introduction or conclusion
- Context the reader needs

Present the archipelago as a numbered outline with clear section headers.

### Phase 3: Draft Connecting Prose

With the Archipelago in place, draft the connections between stepping stones.

**Drafting approach:**
- Write transitions between the IPs the user provided
- Maintain the user's voice and style (ask for a writing sample if unsure)
- Mark clearly what is the user's original text vs. new connective tissue
- Keep drafts intentionally rough -- polishing comes later

**Offer the user choices:**
> "I can draft this in several ways:
> A) Full draft with your IPs woven in -- ready for your editing pass
> B) Section-by-section -- I draft one section, you review, then next
> C) Outline with topic sentences only -- you fill in the prose"

### Phase 4: Dial Down the Scope

When the project feels too large, too complex, or the user is overwhelmed:

**Step 1:** Ask the user to list everything they planned to include.

**Step 2:** For each item, classify as:
- **Essential** -- the output makes no sense without it
- **Important** -- adds significant value but not required
- **Nice-to-have** -- would enhance but can wait

**Step 3:** Propose a Minimum Viable Output using only Essential items.

**Step 4:** Save Important and Nice-to-have items as IPs for a future version.

| Original Scope | Dialed Down Version |
|----------------|-------------------|
| Write an entire book | Write one chapter or a long article |
| Build a full course | Record a single workshop or tutorial |
| Create a 50-slide deck | Create a 10-slide version with key points |
| Write comprehensive report | Write an executive brief with appendix |

> "A finished, imperfect version is infinitely more valuable than an unfinished,
> perfect one. The cut material is saved in your Second Brain as IPs for Version 2."

## Output Formats

Adapt the final output to what the user needs:

| Output Type | Structure |
|------------|-----------|
| **Article/Blog post** | Hook → Context → Main argument → Supporting points → Conclusion → CTA |
| **Presentation** | Title → Problem → Key insights (1 per slide) → Implications → Next steps |
| **Report** | Executive summary → Background → Findings → Analysis → Recommendations |
| **Email/Proposal** | Context → Value proposition → Specific ask → Next step |
| **Documentation** | Overview → Setup → Usage → Examples → Troubleshooting |

## After Expressing

Once the output is drafted:

1. **Extract new IPs** from the work -- sections, research, templates, or frameworks
   that could be reused in future projects
2. **File IPs** back into appropriate PARA folders (Resources or relevant Projects)
3. **Write a Hemingway Bridge** if the work continues in another session -- invoke
   the `hemingway-bridge` skill for this
4. **Celebrate shipping.** Every finished output, no matter how small, builds momentum.

## Key Principles

- **Start with existing material.** Never face a blank page when you have a Second Brain.
- **Separate divergence from convergence.** Gathering IPs (divergent) and sequencing
  them (convergent) are different cognitive modes. Don't mix them.
- **Ship smaller, not later.** Dial Down the Scope beats delaying indefinitely.
- **Every output creates new IPs.** The express cycle is generative, not extractive.
- **Express early and often.** Don't wait until everything is "ready."

## Reference Files

For detailed creative technique descriptions:
- **`../para-organize/references/creative_techniques.md`** -- Full Intermediate Packets, Archipelago of Ideas, Hemingway Bridge, Dial Down the Scope methodology