Documentation Request - How to iterate?

[MauScheff]

It's very clear how to start a new project in README.md, but if I have an existing project how can I test SpecKit on a feature?

[acgxv]

Just /specify what you want to do within this iteration. Works good on my projects.

[MauScheff]

Interesting, thanks! @aurexav

Going to try it!

[quentinbadoud]

So If i detect a bug for exemple, I have to:

/specify
then /plan
then /task
then /implement

??

Not sure to get it right

[MauScheff]

I stopped using Spec-Kit, I found that for me it made more problems than it solved. I would be curious to hear of people using SpecKit everyday.

…

On Thu 19 Feb 2026 at 10:30 quentinbadoud ***@***.***> wrote: *quentinbadoud* left a comment (github/spec-kit#1118) <#1118 (comment)> So If i detect a bug for exemple, I have to: /specify then /plan then /task then /implement ?? Not sure to get it right — Reply to this email directly, view it on GitHub <#1118 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAA3NC4ZH3665OS7XVRM4E34MV7B3AVCNFSM6AAAAACLENN5J2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTSMRVHA3TKMJUGI> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[jaccozilla]

I'm also wondering how people iterate, I've been trying running the /specify -> /plan -> /task -> /implement loop, but every implement takes over an hour (same as the original implement)

I'm trying feedback from github comments to power the next loop, often they are rather minor things such as naming, additional tests, ect where an hour to iterate feels to slow

[mnriem]

See https://github.com/github/spec-kit?tab=readme-ov-file#-community-walkthroughs