addyosmani / addyosmani/agent-skills

Recommended way to handle V2 features without polluting V1 spec?

Open
#150 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
93.8k
Forks
10k
Avg merge
3d 15h
Merged PRs (30d)
23

Description

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!

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.