Save Session Progress FAQs

Question 1

How does this skill improve my workflow?

Accepted Answer

It significantly reduces the time spent on context recovery. By maintaining a structured TASKS.md file, it allows you to restart work after a session clear in approximately 30 seconds, keeping your momentum high and preventing lost effort.

Question 2

When should I use this skill?

Accepted Answer

You should invoke this skill before running the `/clear` command, after completing a major milestone (like a PRP), or whenever you are wrapping up a coding session to ensure all progress is safely logged and committed.

Question 3

What specific information is tracked during a save?

Accepted Answer

The skill tracks recently completed tasks, current phase progress, session history, and critical quality metrics such as test coverage and performance gates, ensuring a comprehensive audit trail of your development.

Question 4

What does the Save Session Progress skill do?

Accepted Answer

This skill automates the documentation of your development work by updating status files like TASKS.md and committing changes to version control. It acts as a project-level bookmark that allows the AI to remember exactly where a project stands.

Question 5

Does this skill require a Git repository?

Accepted Answer

While it is optimized for Git integration to provide version control safety, it is designed to be flexible. If Git is not initialized, the skill will still update your local documentation files and notify you to consider initializing a repository.

Save Session Progress

Save Session Progress

주요 기능

사용 사례

주요 기능

사용 사례