Problem
rules/common/git-workflow.md currently mixes two distinct concerns:
- Git workflow — commit message format, PR process (directly git-related)
- Feature Implementation Workflow — plan → TDD → code review → commit (a general development process)
The "Feature Implementation Workflow" section describes the full development pipeline before code enters git, but placing it in git-workflow.md is confusing — it implies that planning and TDD are part of the git workflow, when they're really about development process.
Suggestion
Split the Feature Implementation Workflow into a separate file (e.g., rules/common/development-workflow.md), and keep git-workflow.md focused on git-specific concerns (commit messages, branching, PR workflow).
This would make both files clearer and easier to understand at a glance.
Problem
rules/common/git-workflow.mdcurrently mixes two distinct concerns:The "Feature Implementation Workflow" section describes the full development pipeline before code enters git, but placing it in
git-workflow.mdis confusing — it implies that planning and TDD are part of the git workflow, when they're really about development process.Suggestion
Split the Feature Implementation Workflow into a separate file (e.g.,
rules/common/development-workflow.md), and keepgit-workflow.mdfocused on git-specific concerns (commit messages, branching, PR workflow).This would make both files clearer and easier to understand at a glance.