TTMusic/openspec/changes/improve-git-collaboration-workflow/specs/git-collaboration-policy/spec.md

ADDED Requirements

Requirement: Protected trunk and short-lived working branches

The repository workflow MUST require all feature development to happen on short-lived branches, and trunk branches MUST be integrated through reviewed pull requests.

Scenario: Developer starts new work item

• WHEN a developer starts implementation for a new task
• THEN the developer MUST create and use a feature/* or fix/* branch instead of committing directly to trunk

Scenario: Code is merged to trunk

• WHEN a branch is ready for integration
• THEN the change MUST be merged through a pull request with review instead of direct push to trunk

Requirement: Standard daily sync flow

The team sync process MUST use a consistent sequence (status check, fetch, then branch update) to reduce avoidable merge conflicts.

Scenario: Branch is up to date before coding

• WHEN a developer begins or resumes work
• THEN the developer MUST verify working tree status and synchronize the branch using the documented standard sequence

Scenario: Shared branch update occurs

• WHEN remote commits are detected on the tracked base branch
• THEN the developer MUST update local branch history using the defined sync strategy before continuing new commits

Requirement: Consistent commit and integration checkpoints

The workflow MUST define minimum checkpoints for commit quality and pull request readiness before integration.

Scenario: Developer prepares to push

• WHEN local commits are ready to publish
• THEN commit messages and change grouping MUST follow the repository contribution policy

Scenario: Pull request is opened

• WHEN a pull request is submitted for review
• THEN it MUST include required context (scope, impact, validation evidence) defined by the collaboration policy