Session Save & Sync FAQs

Question 1

What happens if I perform work that wasn't in the original plan?

Accepted Answer

The skill identifies 'Unplanned work' by finding changes that don't map to existing requirements. It then offers to add these as new requirements or log them as refactors/bug fixes.

Question 2

Does it support multiple active plans?

Accepted Answer

Yes, it reads the status of all active plans associated with a feature and can update multiple plan files in a single session save operation.

Question 3

Does this skill modify my source code?

Accepted Answer

No, Session Save is designed to update your documentation files (like requirements.md, plan files, and session logs) to reflect the state of your code, rather than changing the code itself.

Question 4

Can I use this with any git branching strategy?

Accepted Answer

It works most efficiently with feature branches (e.g., feature/name), but it also allows you to manually specify a feature name to ensure your documentation syncs correctly regardless of branch names.

Question 5

How does Session Save detect my work progress?

Accepted Answer

The skill analyzes your git staged and unstaged changes, along with the commit history on your feature branch, to understand the semantic impact of your work compared to your requirements.

Session Save & Sync

주요 기능

사용 사례

Session Save & Sync

주요 기능

사용 사례