Run the script:
```
./run-sessions.sh
```
Review session details:
- Session number and title
- Tasks to complete
- Deliverables expected
- Time estimate
- Any special notes or dependencies
Press ENTER to see the Claude Code prompt
Copy the prompt and start Claude Code:
```
claude-code
```
Then paste the prompt
Work through the session with Claude Code
When done, press ENTER at the next prompt to mark complete and advance

Resuming Work

The script automatically remembers where you left off:

./run-sessions.sh
# Will start at the last incomplete session

Skipping Sessions

If you want to skip a session (e.g., it's already complete or you want to do it later):

When prompted, press s instead of ENTER
The script will advance to the next session

Resetting Progress

To start over from Session 1:

rm .session-state
./run-sessions.sh

Or manually edit .session-state to the desired session number:

echo "5" > .session-state  # Start at Session 5

Session Overview

Sprint 4: Deploy-Ready Platform (Sessions 1-4)

Session 1: CV Upload Button Component (2-3 hours)
Session 2: CV Upload Modal Component (2-3 hours)
Session 3: Admin Navigation Component (2-3 hours)
Session 4: Mobile & Cross-Browser Testing (3-4 hours)
🚀 DEPLOY CHECKPOINT - Platform ready for production

Sprint 5: Knowledge Base Feature (Sessions 5-15)

Session 5: KB Backend Entities & Repositories (3-4 hours)
Session 6: KB Backend Service Layer (4-5 hours)
Session 7: KB Backend REST API (3-4 hours)
Session 8: KB Frontend Core Components (4-5 hours)
Session 9: KB Frontend Widgets & Features (3-4 hours)
Session 10: Admin CMS - Article Management (4-5 hours)
Session 11: Admin CMS - Analytics Dashboard (3-4 hours)
Session 12: KB Content Writing - Part 1 (Articles 1-10) (15-20 hours) ⚠️
Session 13: KB Content Writing - Part 2 (Articles 11-20) (15-20 hours) ⚠️
Session 14: Final Testing & Bug Fixes (4-6 hours)
Session 15: Deployment Preparation (3-4 hours)
🚀 SPRINT 5 COMPLETE - KB feature ready

Post-Sprint Cleanup (Sessions 16-17)

Session 16: SCSS Optimization (4-6 hours) ⚠️ DEPRIORITIZED
Session 17: Documentation Cleanup (4-6 hours)

Tips

For Long Sessions

Sessions 12 and 13 (content writing) are 15-20 hours each. Consider:

Breaking them into multiple Claude Code sessions
Doing 2-3 articles per Claude session
Taking breaks between articles

Parallel Work

Some sessions can run in parallel if you have multiple people:

Session 3 (Admin Nav) can run parallel to Sessions 1-2
Sessions 5-7 (Backend) can run parallel to Sessions 8-9 (Frontend)
Session 12-13 (Content) can overlap with Sessions 10-11 (CMS)

Session Dependencies

The script shows dependencies, but here are the key ones:

Session 2 depends on Session 1 (modal needs button)
Sessions 6-7 depend on Session 5 (services need entities)
Sessions 8-9 depend on Session 7 (frontend needs API)
Sessions 10-11 depend on Sessions 5-7 (CMS needs backend)
Sessions 12-13 depend on Session 10 (content needs CMS)

Troubleshooting

Script won't start:

chmod +x run-sessions.sh
./run-sessions.sh

Session state file is corrupted:

rm .session-state
# Will reset to Session 1

Want to jump to specific session:

echo "8" > .session-state
./run-sessions.sh

Colors not displaying correctly: The script uses ANSI color codes. If your terminal doesn't support them, they'll show as codes. Most modern terminals (iTerm2, Terminal.app, etc.) support colors.

Example Workflow

# Day 1: Sessions 1-3 (Sprint 4 start)
./run-sessions.sh
# Complete Session 1 (CV Button)
# Complete Session 2 (CV Modal)
# Complete Session 3 (Admin Nav)
# Quit (press 'q')

# Day 2: Session 4 (Sprint 4 complete)
./run-sessions.sh
# Resumes at Session 4 (Testing)
# Complete Session 4
# 🚀 DEPLOY TO PRODUCTION

# Day 3-4: Sessions 5-7 (KB Backend)
./run-sessions.sh
# Complete Sessions 5, 6, 7

# Day 5-6: Sessions 8-11 (KB Frontend & CMS)
./run-sessions.sh
# Complete Sessions 8, 9, 10, 11

# Week 2: Sessions 12-13 (Content Writing)
# Break into multiple days/sessions

# Final: Sessions 14-17 (Testing & Cleanup)
./run-sessions.sh
# Complete final sessions
# 🎉 PROJECT COMPLETE

Integration with Claude Code

The script provides ready-to-use prompts for Claude Code. For each session:

Script shows: Session details and tasks
You press ENTER: See the Claude Code prompt
Copy the prompt: Displayed in clear format
Start Claude Code: claude-code command
Paste prompt: Into Claude Code
Work together: Claude implements the session
Confirm complete: Press ENTER when done

The prompts reference SESSION_PLAN.md which contains all the detailed specifications for each session.

Files Created/Modified

.session-state - Tracks current session (git ignored)
SESSION_PLAN.md - Detailed session specifications
run-sessions.sh - This script

Support

If you encounter issues:

Check SESSION_PLAN.md for detailed session requirements
Review .session-state file (should contain a number 1-17)
Ensure script is executable: chmod +x run-sessions.sh
Check you're in the project root directory

Happy coding! 🚀

Generated with Claude Code

Reacties

Nog geen reacties

Athena — mahmoud-consultancy/archive/old-docs/SESSION_RUNNER_README.md

Session Runner Script - Usage Guide

Quick Start

Features

Session State Tracking

Interactive Controls

Visual Indicators

Workflow

Starting a Session