Add missing critical steps to flow with subheading format

- Added Step 1: Project Analysis
- Added Step 2: Intelligent Crew Selection (was missing!)
- Added Step 3: Context Window Calculation (was missing!)
- Added Step 4: Context Optimization - THE CRITICAL STEP
- Restructured as subheadings instead of table for better readability
- Now properly shows the complete 9-step flow
- Emphasized context optimization as the key innovation

source/README.md

@@ -140,14 +140,37 @@ This completes the flow.
 
 ### Complete Flow Sequence
 
-| Step | Action | Description |
-|------|--------|-------------|
-| 1 | **Copy to temp** | Crew gets copied to a temporary directory for processing |
-| 2 | **Variable insertion** | Crew configs are edited slightly for the task at hand through variable substitution |
-| 3 | **Deploy to workspace** | Processed crew gets copied into the project directory at `./.claude/agents` |
-| 4 | **Generate overview** | CLAUDE.md gets created in the workspace containing a brief overview of the crew |
-| 5 | **Confirmation** | User receives success message confirming their repo has been created with an optimized team of subagents that won't overrun context |
-| 6 | **Reusability** | User can create as many stock agents as they wish, knowing they'll be kept safe in the library and assembled when needed for future projects |
+#### Step 1: Project Analysis
+HTPG evaluates the project specification and requirements that the user is proposing.
+
+#### Step 2: Intelligent Crew Selection
+HTPG draws up a shortlist of subagents from the Agent Farm to form a "crew" with minimal task overlap and maximal synergy for the specific project needs.
+
+#### Step 3: Context Window Calculation
+HTPG calculates the approximate cumulative context window that the desired crew would impose on the system.
+
+#### Step 4: Context Optimization (The Critical Step!)
+If the crew exceeds the user-defined context limit, HTPG makes intelligent substitutions until an optimized crew is assembled that fits within constraints. Tactics include:
+- Removing least important subagents
+- Truncating descriptions or shortening system prompts of constituent agents
+
+#### Step 5: Crew Staging
+Selected and optimized crew gets copied to a temporary directory for processing.
+
+#### Step 6: Config Adaptation
+Crew configs are edited for the task at hand through variable substitution, giving cookie-cutter subagents project-specific context.
+
+#### Step 7: Deployment to Workspace
+Processed crew gets copied into the project directory at `./.claude/agents`.
+
+#### Step 8: Documentation Generation
+CLAUDE.md gets created in the workspace containing a brief overview of the assembled crew and their roles.
+
+#### Step 9: User Confirmation
+User receives a success message confirming their repo has been created with an optimized team of subagents that won't overrun context.
+
+### The Result
+Users can create as many stock agents as they wish, knowing they'll be kept safe in the Agent Farm library and intelligently assembled when needed for future projects.
 
 ## Reference