| name | generating-continuations |
| description | Generate timestamped continuation files for resuming work across chat sessions, tracking beads progress and git status |
Generating Continuations - Spanish Academic Network
Purpose: Generate a timestamped continuation file for resuming work in a new chat session.
Invocation triggers:
- "generate continuation"
- "create continuation file"
- "save session progress"
- "end session"
npm run continue(via execute_continuation.js script)
Instructions for AI Agent
When this skill is invoked, execute the following steps:
Step 1: Query Project State
Run these commands and capture output:
bd list --json # All beads with status
bd ready --json # Next available beads
git status --short # Uncommitted changes
Parse the results:
- Count completed beads (status: "closed")
- Count in-progress beads (status: "in_progress")
- Identify next bead (first item from
bd ready) - List last 5 completed beads
Step 2: Determine Current Phase
Read GETTING_STARTED.md and find the phase marked with ← CURRENT or the phase containing the next ready bead.
Extract:
- Phase number
- Phase title
- Next bead in that phase
- Estimated time for next bead
Step 3: Generate Timestamped File
Filename format: YYYY-MM-DD_HH-MM-SS.md (e.g., 2025-10-24_18-30-45.md)
Location: .claude/skills/generating-continuations/references/continuations/
Content template:
# Continuation: Spanish Academic 2026
**Generated:** [ISO 8601 timestamp]
**Session End:** [Human-readable date and time]
---
## Progress Summary
✅ **Completed Beads:** [COUNT] / 92
**Recent Completions (last 5):**
- spanish-academic-44: Document mobile-first design principles ✅
- spanish-academic-45: Document localization-first principles ✅
- spanish-academic-46: Implement URL mirroring structure ✅
- spanish-academic-47: Create slug translation mapping system ✅
- spanish-academic-1: Build generate_page_json.js script ✅
📋 **In Progress:** [COUNT]
[List in-progress beads with ID and title, or "None"]
⏳ **Ready to Start:** [COUNT]
[List next 5 ready beads with ID and title]
---
## Current Phase
**Phase [N]: [Phase Title]**
**Next Bead:** spanish-academic-[ID]
**Title:** [Bead title from bd ready]
**Description:** [Bead description from bd list]
**Priority:** [Priority from beads system]
**Estimated Time:** [From GETTING_STARTED.md if available]
**See:** [GETTING_STARTED.md](../../../../../../GETTING_STARTED.md) for full roadmap
---
## Recent Changes
**Git Status:**
```
[Output of git status --short]
```
**Files Created/Modified This Session:**
[Parse git status output - list files with M/A/D/? indicators and paths]
---
## Project Context
**Location:** `m:\VS SpAca\spanish-academic\`
**Architecture:** Static-first with React islands, bilingual (/ ↔ /es/)
**Governance:** See [CLAUDE.md](../../../../../../CLAUDE.md) for inviolable rules
**Documentation:**
- [MOBILE_FIRST.md](../../../../../../docs/MOBILE_FIRST.md) - Responsive design principles
- [LOCALIZATION_FIRST.md](../../../../../../docs/LOCALIZATION_FIRST.md) - Bilingual architecture
- [PHASE_ORDER_RATIONALE.md](../../../../../../docs/PHASE_ORDER_RATIONALE.md) - Why scripts before templates
- [CONTINUATION_SYSTEM_IMPLEMENTATION.md](../../../../../../docs/CONTINUATION_SYSTEM_IMPLEMENTATION.md) - Continuation system docs
---
## Key Commands
```bash
# Beads management
bd ready # Show ready beads
bd list --json # List all beads with status
bd update <id> --status in_progress # Start working on a bead
bd close <id> --reason "..." # Complete a bead
# Build & validation
npm run generate-json # Create JSON twins
npm run validate-localization # Check bilingual parity
npm run validate-skills # Validate skill compliance
npm run accessibility-scan # WCAG AA validation
npm run type-check # TypeScript compilation
# Development
npm run dev # Start Vite dev server
npm run build # Build React islands
npm run preview # Preview production build
# Continuation (session management)
npm run continue # Generate continuation file (end session)
```
---
## Next Steps
1. **Start next bead:**
```bash
bd update spanish-academic-[ID] --status in_progress
```
2. **Follow instructions** in GETTING_STARTED.md Phase [N]
3. **Validate work** using appropriate npm scripts as they become available
4. **Close bead** when complete:
```bash
bd close spanish-academic-[ID] --reason "Clear description of what was completed"
```
---
**Ready to continue! Next bead: spanish-academic-[ID] - [Title]**
Step 4: Output Confirmation
After generating the file, output:
✅ Continuation saved: .claude/skills/generating-continuations/references/continuations/[filename]
📋 Summary:
- Completed: [N] beads
- In Progress: [N] beads
- Next: spanish-academic-[ID] - [Title]
- Phase: [Phase N] - [Phase title]
💡 Next session: Say "continue from where we left off"
Claude will automatically find and load this continuation.
Instructions for Resuming (New Session)
When user says "continue from where we left off" or similar phrases:
Step 1: Find Latest Continuation
Scan .claude/skills/generating-continuations/references/continuations/ directory for files matching pattern YYYY-MM-DD_HH-MM-SS.md
Algorithm:
- List all .md files in continuations/ directory
- Exclude
CONTINUATION_PROMPT.md(archived original) - Parse filenames to extract timestamps
- Sort by timestamp (descending)
- Select the first (most recent) file
Step 2: Load and Present Summary
Read the latest continuation file and present a concise summary:
📂 Loading continuation from [date/time]...
✅ Progress: [N] beads completed in Phase [X]
🎯 Next: Bead [ID] - [Title]
📋 Phase: [Current phase number and title]
⏱️ Est. Time: [Time estimate]
[Brief 1-2 sentence description of what the next bead involves]
Ready to start bead [ID]?
Step 3: Wait for Confirmation
Ask user if they want to:
- ✅ Proceed with next bead (start working immediately)
- 📊 Review completed work (show more detail from continuation)
- 🔍 Check project status (run bd ready, git status)
- 📖 Read documentation first (suggest relevant docs)
Default: If user confirms, proceed directly to marking the next bead as in_progress and beginning work.
Expansion Points
This skill can be enhanced to include additional information.
Current Expansion Points:
- ✅ Beads system state (completed, in-progress, ready)
- ✅ Current phase from GETTING_STARTED.md
- ✅ Git status (uncommitted changes)
- ✅ Next bead details
- ✅ Key commands reference
Future Expansion Ideas:
- Code quality metrics (lint errors, type errors)
- Test coverage reports
- Bundle size tracking
- Lighthouse score history
- Dependency updates needed
- Security audit results
- Documentation coverage
- Performance metrics
- Validation script pass/fail summary
- Recent beads velocity (beads completed per session)
How to Expand:
- Add new query commands in Step 1
- Add new sections to the continuation template in Step 3
- Update the output confirmation in Step 4
- Document expansion in CONTINUATION_SYSTEM_IMPLEMENTATION.md
This skill is designed to grow with the project's needs.
Error Handling
If any command fails during execution:
- Log the error but continue generating the continuation
- Mark failed sections with ⚠️ and error message
- Include troubleshooting info in the continuation file
Example:
## Git Status
⚠️ Error running git status: Not a git repository
This ensures the continuation is still generated even if some queries fail.
Related Skills
- validating-localization - Check bilingual parity before ending session
- validating-skills - Validate skill compliance before ending session
Notes
- This skill is invoked both by Claude directly (plain language) and programmatically (npm script)
- The logic is intentionally detailed so it can be implemented in Node.js (
execute_continuation.js) - Continuation files are never deleted automatically - manual cleanup required if disk space becomes an issue
- Relative paths in continuation files assume they're being read from the references/continuations/ directory
- The skill uses 7 levels of
../to reach project root from.claude/skills/generating-continuations/references/continuations/
Last Updated: 2025-10-25 Version: 2.0.0 (Migrated to Anthropic standards)