fix(docs): align superpowers guide with brainstorm-to-branch conventions#3587
Conversation
1a3269a to
327a173
Compare
|
@cbini - This makes sense to me. One question: did we find a resolution for using worktrees in that we ended up with duplicate projects? Could we add something as to when it is better to use a worktree vs a branch? I am not very clear on that. |
|
i forget exactly what the problem was with worktrees, but it's fixed. also it was a dbt power user issue. there is an explanation about the difference -- does it need more context? |
@cbini - So, it sounds like Worktree is like Fork. Sorry to beat a dead horse here, but maybe we should add specific examples of when Branch vs Worktree makes more sense? I just don't know when I would ever need Worktree. Maybe that's more for, like, data mart work? |
|
yeah it's not a fork. i'll clarify it some more |
Reorder Phases 1-2 so the GitHub issue and branch are created before the spec file is written (matching CLAUDE.md's brainstorm-to-branch discipline). Add worktree vs branch switch choice, branch naming convention, and git resuming tip. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Add prose descriptions and comparison table to help users choose between branch switch and worktree workflows. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
37488d1 to
6d1d386
Compare
|
@GabyRangelB updated |

Summary
<gh-username>/<commit-type>/claude-<brief-description>mainbefore resuming work on an existing branchWhy
The original draft had the spec file written before the GitHub issue and branch were created. CLAUDE.md requires: (1) issue before design doc, (2) ask user worktree or branch switch, (3) no files written until on the feature branch.
🤖 Generated with Claude Code