Detailed Examples

Task 1: Analyze the 3 job postings and extract top 10 skills (parallel)
Task 2: Review current resume and identify gaps (depends on Task 1)
Task 3: Rewrite experience section to emphasize required skills (depends on Task 2)
Task 4: Add skills section with keywords (depends on Task 1)
Task 5: Proofread and format (depends on Task 3, Task 4)

Task 1: Analyze job postings and extract top 10 skills
Task 2: Review current resume and identify gaps (depends on Task 1)
Task 3: Rewrite experience section to emphasize required skills (depends on Task 2)
Task 4: Proofread and format (depends on Task 3)

[Task 1/4] ✓ Analyzed 3 job postings
  Top skills: Python (all 3), AWS (2/3), System Design (2/3), Leadership (all 3), React (2/3)

[Task 2/4] ✓ Reviewed resume gaps
  Have: Python, Leadership
  Missing: AWS, System Design deep dive, React specifics

[Task 3/4] ✓ Rewrote experience section
  Added AWS/EC2 project details
  Expanded system design examples
  Mentioned React contributions

[Task 4/4] ✓ Proofread and formatted
  Fixed typo in "architected"
  Aligned bullet points

Task 1: Check request size limits
Task 2: Check database query performance
Task 3: Check network timeout settings
Task 4: Monitor actual timeout location if still failing

[Task 1/4] ✓ Checked request size limits
  Limit: 100MB
  Actual large request: 50MB
  Not the issue.

[Task 2/4] ✓ Checked database query
  Found: N+1 query bug
  Query takes 45 seconds on large dataset
  Recovery needed.

  Recovery attempt: Add query optimization with joins
  [Task 2/4 RETRY] ✓ Query now takes 2 seconds

[Task 3/4] ✓ Checked timeout settings
  Timeout: 30 seconds
  With optimized query: well within limit

[Task 4/4] — Skipped (no longer needed, issue was Query optimization)

Task 1: Run full test suite (no side effects)
Task 2: Review deployment plan with team (approval gate)
Task 3: Deploy to staging (test before prod)
Task 4: Run smoke tests on staging
Task 5: Deploy to production (irreversible)
Task 6: Monitor production for 1 hour

Task 1: Run full test suite
Task 2: Create rollback procedure and document it
Task 3: Review deployment with team (approval gate)
Task 4: Deploy to staging
Task 5: Run smoke tests on staging
Task 6: Deploy to production
Task 7: Monitor for 1 hour and rollback if needed

[Task 1/7] ✓ Full test suite passing (1200 tests)

[Task 2/7] ✓ Created rollback procedure
  Documented: database migration rollback, service restart order, config revert

[Task 3/7] GATE: Team review requested
  Team approves deployment plan at 2:00 PM

[Task 4/7] ✓ Deployed to staging

[Task 5/7] ✓ Smoke tests passed
  Login works, token validation works, SSO works

[Task 6/7] ✓ Deployed to production

[Task 7/7] ✗ Production monitoring: 5% login failure rate detected at 2:15 PM
  
  Recovery: ROLLBACK (prepared in Task 2)
  [Task 7/7 RECOVERY] ✓ Rolled back to previous version
  Login failure rate drops to 0.1% (baseline)
  
  Analysis: New SSO integration failing for 5% of users
  Escalated to auth team for investigation

Task 1: Define typo types we want to catch (spell check, double spaces, punctuation)
Task 2: Write function skeleton with docstring
Task 3: Implement spell check using dictionary
Task 4: Implement double-space detection
Task 5: Implement punctuation checks
Task 6: Write unit tests
Task 7: Test against sample resumes

Task 1: Define typo types AND approved jargon list

[Task 1/7] ✓ Defined typo types and jargon whitelist
  Typos: misspellings, double spaces, incorrect punctuation
  Jargon: synergize, leverage, ideate, pivot, etc.

[Task 2/7] ✓ Function skeleton written

[Task 3/7] ✓ Spell check implemented

[Task 4/7] ✓ Double-space detection implemented

[Task 5/7] ✓ Punctuation checks implemented

[Task 6/7] ✓ Unit tests written (15 tests)

[Task 7/7] ✓ Tested against 5 sample resumes
  False positive rate: 2% (acceptable)
  Caught real typos: 92% detection rate