spec.md 1.9 KB
ADDED Requirements
Requirement: Pull safety check for local modifications
The workflow MUST require developers to inspect and protect local modifications before any pull, rebase, or branch switch operation.
Scenario: Working tree contains uncommitted changes
- WHEN a developer is about to run a sync operation and local changes exist
- THEN the process MUST require explicit protection through commit or stash before sync continues
Scenario: Working tree is clean
- WHEN a developer runs pre-sync checks and no local changes exist
- THEN the sync operation MAY proceed directly using the standard update flow
Requirement: Recoverable stash and temporary backup strategy
The workflow MUST define a recoverable backup path for temporary local work, including naming and restore steps.
Scenario: Developer parks in-progress work
- WHEN a developer cannot commit current changes but must synchronize first
- THEN the workflow MUST support creating a named stash or temporary backup branch with restoration instructions
Scenario: Developer restores protected changes
- WHEN sync is complete and in-progress work needs to be resumed
- THEN the workflow MUST provide deterministic restore steps and conflict-handling guidance
Requirement: High-risk command guardrails
The collaboration policy MUST define restricted destructive Git commands and required safeguards before any forced history or workspace reset action.
Scenario: Developer considers destructive cleanup
- WHEN a developer plans to use commands that can discard local changes
- THEN the workflow MUST require explicit confirmation and a documented recovery point first
Scenario: Accidental overwrite risk is identified
- WHEN a potential overwrite or data-loss situation is detected
- THEN the workflow MUST direct the developer to the documented recovery SOP instead of continuing destructive operations