O

Step 8: Technical Review

context engineering new guide creation plan

Step 8: Technical Review

Goal

Final quality check focusing on technical accuracy, formatting correctness, readability, and export-readiness. This is the last review before publishing.

Inputs Required

| Input | Source | Purpose | |-------|--------|---------| | All chapters | guide_draft/*.md | Content to review | | Document spec | document_spec.md | Technical standards | | Completeness review | review_completeness.md | Issues already identified |

Review Areas

1. Factual Accuracy - Are claims correct?
2. Technical Accuracy - Are code/prompts correct?
3. Citation Accuracy - Are quotes accurate?
4. Formatting - Is markdown correct?
5. Readability - Is language clear?
6. Export Testing - Does it convert properly?

Process

8.1 Factual Accuracy Review

Verify claims are accurate:

## Factual Claims Check

| Claim | Location | Verification | Status |
|-------|----------|--------------|--------|
| "Chroma Research shows performance degrades..." | Ch 3.2 | Verified against source | ✅ |
| "Karpathy coined 'context engineering'" | Ch 1.3 | He endorsed, didn't coin | ⚠️ Fix wording |
| "AI models are trained to be agreeable" | Ch 4.1 | Generally accepted | ✅ |
| "2-minute rule for AI response" | Ch 3.4 | Author's experience | ✅ (opinion) |
| ... | ... | ... | ... |

### Claims Needing Verification
- [ ] [Claim] - need to verify [source]
- [ ] [Claim] - need to verify [source]

### Claims Needing Softening
- [ ] [Claim] - change "always" to "usually"
- [ ] [Claim] - add "in my experience"

8.2 Technical Content Review

Verify code and prompts are correct:

## Technical Content Check

### Code Blocks
| Code Block | Location | Syntax | Logic | Status |
|------------|----------|--------|-------|--------|
| Email validation example | Ch 2.3 | ✅ | ✅ | OK |
| Task template | Ch 2.4 | ✅ | N/A | OK |
| Bad prompt example | Ch 3.1 | ✅ | N/A | OK |
| ... | ... | ... | ... | ... |

### Prompt Examples
| Prompt | Location | Realistic | Works | Status |
|--------|----------|-----------|-------|--------|
| "Fix this bug" example | Ch 1.2 | ✅ | N/A | OK |
| SQL optimization | Ch 5.2 | ✅ | ✅ Tested | OK |
| LinkedIn post style | Ch 2.3 | ✅ | ✅ Tested | OK |
| ... | ... | ... | ... | ... |

### Technical Terms
| Term | Usage | Correct | Notes |
|------|-------|---------|-------|
| Context window | Ch 1.4 | ✅ | |
| Token | Ch 3.2 | ⚠️ | Add brief definition |
| RAG | Ch 5.1 | ❌ | Used but not defined |

8.3 Citation Accuracy

Verify quotes and attributions:

## Citation Verification

### Direct Quotes
| Quote | Attribution | Verified | Status |
|-------|-------------|----------|--------|
| "Context engineering is the delicate art..." | Karpathy | ✅ Twitter, June 2025 | OK |
| "ChatGPT wrapper is tired and wrong" | Karpathy | ✅ Same thread | OK |
| Performance data | Chroma Research | ✅ July 2025 paper | OK |
| ... | ... | ... | ... |

### Paraphrased Content
| Content | Source | Accurate Paraphrase | Status |
|---------|--------|---------------------|--------|
| QA bottleneck concept | Arrowsmith tweet | ✅ | OK |
| Tobi Lutke on AI adoption | Shopify memo | ⚠️ Verify exact stance | Check |
| ... | ... | ... | ... |

### Citations List Complete
- [ ] All cited sources listed in References
- [ ] Links/dates included where applicable
- [ ] No broken links

8.4 Formatting Review

Verify markdown is correct:

## Formatting Check

### Headers
- [ ] Consistent header levels (## for chapters, ### for sections)
- [ ] No skipped levels (## → ####)
- [ ] Headers match table of contents

### Code Blocks
- [ ] All code blocks properly fenced (```)
- [ ] Language hints where applicable (```markdown, ```javascript)
- [ ] No broken code block closings

### Lists
- [ ] Consistent list markers (all - or all *)
- [ ] Proper indentation for nested lists
- [ ] No orphan list items

### Tables
- [ ] All tables render correctly
- [ ] Column alignment consistent
- [ ] No missing cells

### Special Characters
- [ ] ❌ and ✅ render correctly
- [ ] Arrows (→) render correctly
- [ ] Quotes (" ") are consistent (not mixed " and ")

### Links
- [ ] All internal links work
- [ ] All external links work (if any)
- [ ] No broken anchor links

### Common Issues Found
| Issue | Location | Fix |
|-------|----------|-----|
| Missing code fence | Ch 3, line 145 | Add closing ``` |
| Table misaligned | Ch 5, line 230 | Fix column count |
| ... | ... | ... |

8.5 Readability Review

Final language quality check:

## Readability Check

### Sentence Length
- Target: Average 15-20 words
- [ ] No sentences over 40 words
- [ ] Complex sentences broken up

### Paragraph Length
- Target: 3-5 sentences
- [ ] No paragraphs over 7 sentences
- [ ] Single-sentence paragraphs used sparingly

### Jargon Check
| Term | First Use | Defined | Status |
|------|-----------|---------|--------|
| LLM | Ch 1.2 | ✅ | OK |
| Context window | Ch 1.4 | ✅ | OK |
| Token | Ch 3.2 | ❌ | Add definition |
| ... | ... | ... | ... |

### Passive Voice
- [ ] Passive voice minimized
- [ ] Active voice used for instructions

### Reading Level
- Target: Accessible to non-native English readers
- [ ] Avoid idioms or explain them
- [ ] Avoid complex vocabulary when simple works

### Specific Fixes Needed
| Issue | Location | Current | Fix To |
|-------|----------|---------|--------|
| Passive voice | Ch 2.4 | "was processed by" | "processed" |
| Long sentence | Ch 3.1 | 45 words | Split into 2 |
| Undefined term | Ch 5.2 | "RAG" | Add definition |

8.6 Export Testing

Test that guide exports correctly:

## Export Testing

### Markdown Rendering
Test in:
- [ ] GitHub preview
- [ ] VS Code preview
- [ ] Markdown editor of choice

### PDF Conversion
Test with:
- [ ] Pandoc: `pandoc guide.md -o guide.pdf`
- [ ] Or preferred PDF tool

Check:
- [ ] Headers render correctly
- [ ] Code blocks formatted
- [ ] Tables not broken
- [ ] Special characters appear
- [ ] Page breaks reasonable
- [ ] Images/diagrams included (if any)

### Issues Found
| Issue | Export Format | Fix |
|-------|---------------|-----|
| Table breaks across pages | PDF | Add page break before |
| Code block cut off | PDF | Reduce code length |
| ... | ... | ... |

Output: review_technical.md

# Technical Review Results

## Date: [date]
## Reviewer: [name]
## Status: Pass / Needs Revision

---

## Summary

| Area | Status | Issues |
|------|--------|--------|
| Factual Accuracy | ✅/⚠️/❌ | [X] |
| Technical Accuracy | ✅/⚠️/❌ | [X] |
| Citation Accuracy | ✅/⚠️/❌ | [X] |
| Formatting | ✅/⚠️/❌ | [X] |
| Readability | ✅/⚠️/❌ | [X] |
| Export | ✅/⚠️/❌ | [X] |

---

## Critical Issues

1. **[Issue]**
   - Location: [Chapter/Section]
   - Problem: [Description]
   - Fix: [Required action]

---

## Minor Issues

1. **[Issue]**
   - Location: [Chapter/Section]
   - Fix: [Required action]

---

## Final Checklist Before Publish

- [ ] All critical issues fixed
- [ ] All minor issues fixed (or documented as known)
- [ ] Final export tested
- [ ] File named correctly
- [ ] Ready for distribution

---

## Sign-off

Technical review complete. Guide is APPROVED / NEEDS REVISION.

Quality Criteria

| Criterion | Check | |-----------|-------| | All factual claims verified or softened | ☐ | | All code/prompts technically correct | ☐ | | All quotes accurately attributed | ☐ | | Markdown renders correctly | ☐ | | No readability issues | ☐ | | PDF export successful | ☐ | | No broken links | ☐ |

Time Estimate

  • Factual accuracy: 30-45 minutes
  • Technical accuracy: 20-30 minutes
  • Citation verification: 20-30 minutes
  • Formatting review: 30-45 minutes
  • Readability review: 30-45 minutes
  • Export testing: 20-30 minutes

Total: 2.5-4 hours

Decision Point

If PASS:
  → Proceed to Final Assembly
  → Guide ready for publication

If NEEDS REVISION:
  → Fix identified issues
  → Re-run affected review sections
  → Approve when all fixed

Final Assembly

Once technical review passes:

# Combine all chapter files into single document
cat guide_draft/00_introduction.md > CONTEXT_ENGINEERING_GUIDE.md
echo "" >> CONTEXT_ENGINEERING_GUIDE.md
cat guide_draft/01_*.md >> CONTEXT_ENGINEERING_GUIDE.md
echo "" >> CONTEXT_ENGINEERING_GUIDE.md
cat guide_draft/02_*.md >> CONTEXT_ENGINEERING_GUIDE.md
# ... continue for all chapters
cat guide_draft/XX_appendix.md >> CONTEXT_ENGINEERING_GUIDE.md

# Generate PDF
pandoc CONTEXT_ENGINEERING_GUIDE.md -o CONTEXT_ENGINEERING_GUIDE.pdf

Next Step

→ Once technical review passes, proceed to 09_final_checklist.md for pre-publish checklist

Article Details

Category
context engineering new guide creation plan
Published
November 28, 2025
Length
1,571 words
8,731 characters
~7 pages
Status
Draft Preview

Navigate

Back to context engineering new guide creation planAll ArticlesHome

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