First of all, thank you for creating this kind of tool to ensure a good workflow for AI coding ❤️❤️❤️.
- After using the
/specify command, the spec.md file gets created with [FEATURE NAME], I think we could configure the prompt to ensure the name, branch, date are match with the user input and in the header of spec.md, plan.md
- The line
- [x] No [NEEDS CLARIFICATION] markers remain is checked, but the text [NEEDS CLARIFICATION: xxxx] is still in the body of the spec.md file, some users may not be aware and lead to confusion when they pass the spec.md to someone.
- Technical context is not being captured even already mention during the
/plan for example /plan I am going to use Next.js for the frontend, FastAPI for the backend, PostgreSQL for the database, create mock 5-10 records of data during the development, make sure the web app is responsive and ready for mobile. it's produce the result in attached image
- The task.md file gets created by just run
/plan , this may not be a big issue, it's just different from the guide on YouTube.
First of all, thank you for creating this kind of tool to ensure a good workflow for AI coding ❤️❤️❤️.
/specifycommand, the spec.md file gets created with [FEATURE NAME], I think we could configure the prompt to ensure the name, branch, date are match with the user input and in the header of spec.md, plan.md- [x] No [NEEDS CLARIFICATION] markers remainis checked, but the text [NEEDS CLARIFICATION: xxxx] is still in the body of the spec.md file, some users may not be aware and lead to confusion when they pass the spec.md to someone./planfor example/plan I am going to use Next.js for the frontend, FastAPI for the backend, PostgreSQL for the database, create mock 5-10 records of data during the development, make sure the web app is responsive and ready for mobile.it's produce the result in attached image/plan, this may not be a big issue, it's just different from the guide on YouTube.