addyosmani / addyosmani/agent-skills

Recommended way to handle V2 features without polluting V1 spec?

未關閉
#150 1 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視
主要語言
JavaScript
星號
93.8k
分支
10k
平均合併
3 天 15 小時
30 天內合併 PR
23

描述

During /spec I have lots of ideas, many of them I need to leave behind for the V1.
1. Should I mention in the spec that this is a V1, even mention the V2 backlog?
2. After /build and possibly the others including /ship, what is the process to work on the V2 features? Hand-edit spec.md with a following /plan? Lets say I built ontop of Sqlite and now want to move to PostGreSQL. Or I want to remove a manual user step and use OCR instead.

I understand that its probalby best to bring in single new requirements or changes and work on them instead of changing too many at once. Still I am trying to figure out the questions above... Thanks so much for this awesome plugin!

貢獻指南

開啟貢獻指南

評估

這個 Issue 還沒有評估資料。

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。