Step 3: Topic Review & Restructure

Step 3: Topic Review & Restructure

Goal

Review all topic analyses and determine if the original syllabus structure is optimal. Merge, split, reorder, or add topics as needed based on what the analysis revealed.


Inputs Required

| Input | Source | Purpose | |-------|--------|---------| | Original syllabus | syllabus.md | Starting structure | | All topic analyses | topic_analysis/*.md | Detailed content info | | Gap analyses | Within topic analysis files | Missing content |


Process

3.1 Analysis Summary Review

Create a summary view of all analyses:

## Analysis Summary

| Chapter | Content Volume | Gaps Found | Overlap With | Recommendation |
|---------|---------------|------------|--------------|----------------|
| Ch 1 | High (3 articles) | None | Ch 2 intro | Keep as is |
| Ch 2 | Medium | Need more examples | Ch 1 ending | Keep as is |
| Ch 3 | Low | Major gaps | Ch 4 | Consider merge |
| Ch 4 | High | None | Ch 3 | Consider merge |
| Ch 5 | Medium | Tool updates needed | None | Keep, update |
| ... | ... | ... | ... | ... |

Action: Read through all topic analysis files and summarize findings.


3.2 Content Volume Assessment

Check if chapters are balanced:

## Content Volume Check

Target per chapter: 3,000-5,000 words (roughly 6-10 pages)

| Chapter | Estimated Words | Status |
|---------|-----------------|--------|
| Ch 1 | 4,500 | ✅ Good |
| Ch 2 | 5,200 | ✅ Good (slightly long) |
| Ch 3 | 1,800 | ⚠️ Too short |
| Ch 4 | 6,500 | ⚠️ Too long |
| Ch 5 | 3,200 | ✅ Good |

Decisions:

  • Too short → Merge with related chapter OR expand with new content
  • Too long → Split into two chapters OR move content to other chapters

3.3 Gap Resolution

Address gaps identified in topic analyses:

## Gap Resolution Plan

### Critical Gaps (must fix)
| Gap | Chapter | Resolution |
|-----|---------|------------|
| No example for [topic] | Ch 2 | Create new example based on interview Q12 |
| Missing citation for [claim] | Ch 4 | Find external source or soften claim |

### Nice-to-Have Gaps (fix if time allows)
| Gap | Chapter | Resolution |
|-----|---------|------------|
| Could use diagram | Ch 1 | Create prompt vs context visual |
| More tool details | Ch 5 | Add based on Article 6 |

### Gaps to Ignore
| Gap | Chapter | Reason |
|-----|---------|--------|
| [Gap description] | Ch X | Out of scope for this guide |

3.4 Overlap Resolution

Handle content that appears in multiple places:

## Overlap Resolution

| Content | Appears In | Primary Location | Secondary Locations |
|---------|------------|------------------|---------------------|
| AI as colleague metaphor | Ch 1, Ch 3 | Ch 1 (define here) | Ch 3 (reference only) |
| Task template | Ch 2, Ch 6 | Ch 2 (full template) | Ch 6 (reference) |
| Karpathy quote | Ch 1, Ch 7 | Ch 1 (introduce) | Ch 7 (callback) |

**Rule:** Define concepts once, reference elsewhere. Don't repeat full explanations.

3.5 Flow Analysis

Check if the narrative flow makes sense:

## Narrative Flow Check

### Current Flow:
Ch 1: [Topic] → Ch 2: [Topic] → Ch 3: [Topic] → ...

### Reader Journey Questions:
1. After Ch 1, does reader have enough foundation for Ch 2? [Yes/No]
2. Is there a logical progression from problem to solution? [Yes/No]
3. Do practical chapters come after conceptual ones? [Yes/No]
4. Is the ending satisfying (not abrupt)? [Yes/No]

### Flow Issues Found:
- [ ] Ch X should come before Ch Y because [reason]
- [ ] Missing transition between Ch X and Ch Y
- [ ] Reader might be confused at Ch X because [reason]

3.6 Restructure Decisions

Document all structural changes:

## Restructure Decisions

### Merges
| Merge | Original | New | Rationale |
|-------|----------|-----|-----------|
| Ch 3 + Ch 4 | "Mistakes" + "Breaking Down" | "From Mistakes to Mastery" | Both too short, naturally connected |

### Splits
| Split | Original | New Chapters | Rationale |
|-------|----------|--------------|-----------|
| Ch 5 | "Tools & Practice" | "Tools" + "Real Examples" | Too much content, distinct topics |

### Reorders
| Move | From | To | Rationale |
|------|------|-----|-----------|
| Team chapter | Ch 6 | Ch 7 | Should come after individual practice |

### Additions
| New Chapter | Content Source | Rationale |
|-------------|----------------|-----------|
| "Quick Reference" | Presentation 10 advices | Practical value, different format |

### Removals
| Remove | Reason |
|--------|--------|
| Section X.Y | Duplicate of Section Z.W |
| Chapter N | Not enough content, merge with M |

3.7 Revised Syllabus

Create the updated syllabus:

## Syllabus v2.0 (Revised)

### Changes from v1.0:
- Merged Ch 3 and Ch 4
- Split Ch 5 into two chapters
- Reordered Ch 6 and Ch 7
- Added Quick Reference appendix

---

# Part 1: Foundations
## Chapter 1: [New/Updated Title]
### 1.1 [Section]
### 1.2 [Section]

## Chapter 2: [New/Updated Title]
### 2.1 [Section]
...

[Continue with full revised structure]

---

## Updated Coverage Map

| New Chapter | Original Sources | Analysis File |
|-------------|-----------------|---------------|
| Ch 1 (new) | Ch 1 (old) | ch01_analysis.md |
| Ch 2 (new) | Ch 2 (old) | ch02_analysis.md |
| Ch 3 (new) | Ch 3 + Ch 4 (old) | ch03_analysis.md, ch04_analysis.md |
...

Output: syllabus_revised.md

# Context Engineering Guide - Revised Syllabus

## Version: 2.0
## Date: [date]
## Status: Approved for Writing

---

## Change Log
| Version | Date | Changes |
|---------|------|---------|
| 1.0 | [date] | Initial syllabus |
| 2.0 | [date] | [Summary of changes] |

---

## Final Structure

[Full revised syllabus here]

---

## Writing Order

Recommended order for chapter writing:
1. Chapter X - foundation, sets tone
2. Chapter Y - core content
3. ...

*Rationale: [Why this order]*

---

## Dependencies

| Chapter | Depends On | Must Complete Before |
|---------|------------|---------------------|
| Ch 2 | Ch 1 | Ch 3 |
| Ch 3 | Ch 1, Ch 2 | Ch 4 |
...

Quality Criteria

| Criterion | Check | |-----------|-------| | All gaps have resolution plan | ☐ | | No chapter too short (<2,000 words expected) | ☐ | | No chapter too long (>6,000 words expected) | ☐ | | Overlaps resolved (one primary location each) | ☐ | | Flow makes logical sense | ☐ | | All changes documented | ☐ | | Revised syllabus is complete | ☐ |


Decision Framework

When unsure whether to merge/split/reorder, ask:

  1. Merge? → Would a reader naturally expect these together?
  2. Split? → Could these stand alone as separate articles?
  3. Reorder? → Does current position require forward-references?
  4. Remove? → Does this add value, or is it filler?

Common Pitfalls

  1. Over-restructuring - Don't reorganize for the sake of it. If v1 works, keep it.
  2. Losing content - Every merge/removal must account for content. Don't delete insights.
  3. Breaking flow - Test the new flow by reading chapter titles in sequence.
  4. Ignoring analysis - The analysis files have the answers. Re-read them.

Time Estimate

  • Analysis summary: 30-45 minutes
  • Gap resolution planning: 30-45 minutes
  • Overlap resolution: 20-30 minutes
  • Flow analysis: 20-30 minutes
  • Restructure decisions: 30-45 minutes
  • Revised syllabus writing: 30-45 minutes

Total: 2.5-4 hours


Next Step

→ Once syllabus_revised.md is complete and approved, proceed to 04_document_requirements.md

Article Details

Category
context engineering new guide creation plan
Published
November 28, 2025
Length
1,324 words
7,567 characters
~6 pages
Status
Draft Preview

More from context engineering new guide creation plan

Guide Creation Plan - Overview

# Guide Creation Plan - Overview ## Project: Context Engineering PDF Guide ### Purpose Create a comprehensive, shareable PDF guide on Context Engineering based on existing articles, interviews, and ...

Read article

Step 9: Final Checklist & Publication

# Step 9: Final Checklist & Publication ## Goal Final pre-publication checklist and guide assembly. Ensure everything is ready for distribution. --- ## Pre-Publication Checklist ### Content Qualit...

Read article

Step 1: Syllabus Creation

# Step 1: Syllabus Creation ## Goal Create a structured outline of all topics that will be covered in the guide. This becomes the backbone of the entire document. --- ## Inputs Required | Input | ...

Read article