Feedback after few days

[stefanofalasca]

"Let's assume the tool is valid, but in my opinion it still needs some checks / implementations to improve its efficiency:

1. It happened to me several times that the spec folder was generated multiple times in different places. I have a repository with various projects, I started working and using the tool inside a folder of a specific project, sometimes it created the spec folder inside .specify/spec, other times it created them on the main git root.
2. The spec counter doesn't work well; I ended up with two features numbered 001... and 002...
3. I don't like the idea of the tool creating the branch. The way I work, I need to create the branch myself according to my own standard which is then linked to the feature or bug in Azure DevOps.
4. I find tons of comments in the code referring to tasks and user stories without any reference to the feature, therefore practically useless, e.g.:
   // T021 [US4]: Log the interval value
   _logger.LogDebug("Thread 3: Intervallo TempoPausaSinottico: {Minutes} minuti", intervalMinutes);"

[echarrod]

It happened to me several times that the spec folder was generated multiple times in different places. I have a repository with various projects, I started working and using the tool inside a folder of a specific project, sometimes it created the spec folder inside .specify/spec, other times it created them on the main git root.

How are you generating these? Can you share the command?
I just did init once, and then I personally haven't found it generates them in different places, but i'm nearly always at the repo root from command line

[stefanofalasca]

I used :
specify init . --ai claude
/speckit.specify @feature-xxxx.md