# Second Brain

> When to activate: second brain, BASB, Building a Second Brain, CODE method, knowledge management, creative output, insight capture, intermediate packets

- Skill: `mattakushi432/second-brain` (Agent Skill)
- Install (CLI): `npx skillmds@latest add mattakushi432/second-brain`
- Raw SKILL.md: https://api.skillmd.com/api/skills/mattakushi432/second-brain/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: Mattakushi432 (https://skillmd.com/u/mattakushi432)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/mattakushi432/second-brain

---


# Second Brain (BASB)

## Core Premise

Your biological brain is for generating ideas, not storing them. A "second brain" is an external digital system that stores and organizes knowledge so your biological brain stays free for higher-level thinking.

Tiago Forte's Building a Second Brain (BASB) framework: organize for actionability, not for perfect categorization.

## CODE Method

| Step | What it means | Action |
|------|-------------|--------|
| **C**apture | Save what resonates | Use capture tools; keep bar low |
| **O**rganize | Sort by actionability | Use PARA to place it |
| **D**istill | Highlight the essence | Progressive summarization |
| **E**xpress | Create output | Use your notes to make things |

### Capture — What to save
Save anything that:
- Surprises you
- Challenges your current thinking
- Is useful for a current project
- Could be useful for a future project
- Resonates emotionally, even if you don't know why yet

### Capture — What NOT to save
- Everything (curation is the skill)
- Things you can easily Google again
- Raw bookmarks with zero context added
- Items you're saving "just in case" with no project connection

### Organize — PARA
- **Projects**: Active work with outcome + deadline
- **Areas**: Ongoing responsibilities (Health, Finance, Work)
- **Resources**: Topics of interest for future use
- **Archives**: Inactive from any of the above

Sort captured items into PARA at capture time or in weekly review. Project folders get priority — resources exist to support projects.

### Distill — Progressive Summarization
Layer 1: Save the source
Layer 2: Bold key passages (10-20% of text)
Layer 3: Highlight key bolded passages (10-20% of layer 2)
Layer 4: Write executive summary at top

Only add a layer when revisiting for a real reason. Over-summarizing upfront is wasted effort.

### Express — Output
Notes exist to produce output. If you're capturing and organizing but never expressing, the system is incomplete. Every piece of knowledge eventually becomes:
- A document, article, or post
- A decision or recommendation
- A conversation or presentation
- A project plan or design

## Intermediate Packets (IPs)

The core productivity concept of BASB: break creative work into reusable chunks.

| IP type | What it is | Examples |
|---------|-----------|---------|
| Distilled notes | Processed source material | Book summary, research note |
| Outlines | Skeleton structures | Article outline, project plan template |
- Drafts | Early incomplete versions | Rough draft, sketch, prototype |
| Summaries | Condensed versions | Meeting notes, executive summary |
| Templates | Reusable frameworks | Project brief, review template |

**Rule**: Save intermediate work, not just finished products. A rough outline you made 6 months ago can seed a new project instantly.

## Resonance-Based Capture

Don't try to capture everything that might be useful. Capture what resonates — things that create a "hm, interesting" or "I want to think more about this" reaction.

Why resonance works:
- Filters for personal relevance without conscious analysis
- You're more likely to revisit things that moved you
- It's sustainable — you can't read and save everything

Practice: when reading, only highlight when you feel something. Skip the "this seems important" trap.

## Project-Support Organization

Every active project should have its own folder containing:
- Project brief (outcome, deadline, milestones)
- All relevant source material
- Working notes and drafts
- Decision log

When a project closes → archive the folder. Future-you can find it; active-you stays uncluttered.

## 12 Favorite Problems

Richard Feynman kept 12 favorite open questions in his mind. New information got filtered through them — if it helped answer one, he paid close attention.

Your 12 favorite problems are ongoing questions that guide what you capture:

```
Examples:
- How do I build systems that require less willpower to maintain?
- What makes writing genuinely useful vs merely comprehensive?
- How do small teams consistently outperform large ones?
- What's the relationship between constraints and creativity?
```

When capturing, ask: does this help answer any of my 12 favorite problems?

## Knowledge Retrieval Patterns

A second brain is only useful if you can find things. Two retrieval modes:

| Mode | When | How |
|------|------|-----|
| Search | You know what you're looking for | Full-text search by keyword |
| Browse | You're exploring or don't know exact terms | Navigate PARA folders by project/area |

### Making notes findable
- Use consistent vocabulary (pick one term: "PKM" or "knowledge management" — not both)
- Add tags for cross-cutting themes
- Title notes descriptively — the title is the primary findability hook
- Use a dedicated tag for "evergreen" notes worth revisiting

## Maintenance System

### Daily (5 min)
- Add items to capture inbox as you encounter them
- Quick scan of today's project folder before starting work

### Weekly (15 min, during weekly review)
- Process capture inbox to zero
- Add new material to correct PARA folders
- Review project notes for current week's work

### Monthly (30 min)
- Archive completed projects
- Prune resources that are no longer relevant
- Browse 10-15 random notes — update anything outdated

### Quarterly (1 hour)
- Review PARA structure — does it still reflect your life?
- Identify most-used resources → promote to better visibility
- Clean up orphaned notes with no project connection

## Signs the System Is Working

- You find notes when you need them
- Starting a new project, you already have relevant material
- Your writing/work improves because you build on past thinking
- You feel less anxious about forgetting things
- Creative connections appear between unrelated domains

## Signs the System Needs Attention

- Inbox has 500+ unprocessed items
- You can't remember what you saved last week
- Capture rate is high but output rate is zero
- Every search returns too many irrelevant results
- You have 8 "second brain" tools and none feel settled