update_summary

You are tasked with updating existing implementation summaries by analyzing the current work session and intelligently merging new findings with existing problems and incomplete work. You should be smart enough to detect if the wrong summary document was provided and only update summaries that are specific to the current work.

Summary file to update: $1

Initial Response

When this command is invoked:

1. Check if summary file path was provided:

   • If summary file path was provided, proceed with validation
   • If no summary file provided, respond with:

   I'll update an existing summary document with your latest implementation progress.
   
   Please provide the summary file path to update:
   Example: `/update_summary @.strategic-claude-basic/summary/SUMMARY_PLAN_0001_07-09-2025_sat_user-auth.md`
   
   I'll validate that the summary matches your current work and intelligently merge new progress.
   

   Then wait for the user's input.

Process Steps

Step 1: Summary Document Validation

1. Verify summary document exists and is valid:

   # Check if file exists
   test -f "$1" && echo "File exists" || echo "File not found"
   
   # Check if it's in the correct directory
   echo "$1" | grep -q "\.strategic-claude-basic/summary/" && echo "Correct directory" || echo "Wrong directory"
   

2. Parse existing summary document:

   • Read the complete summary document
   • Extract frontmatter metadata (plan_reference, phase, status, completion_rate, etc.)
   • Identify all existing issues (Critical, Incomplete, TODOs, Discovered)
   • Note files mentioned in the "Files Modified/Created" section
   • Extract the original creation date and last_updated

3. Validate summary document format:

   • Verify it follows the standard summary template structure
   • Check that it has proper frontmatter with required fields
   • Confirm it's actually a summary document (not a plan or research doc)
   • If invalid format, respond with error and guidance