Sample issue · Preview, not a previously sent email
A clearer brief. A more useful result.
Try this workflow
Before asking for a change, write its outcome, context, constraints, and evidence. Use one visible example to define success.
Open the project brief template
Understand one change
The September 9 CLI release introduced an experimental worktree flow. Our note separates the documented change from checks you can make in your own project.
Keep one resource
Create a concise repository briefing with your actual paths and validation commands.