How to regenerate artifacts after modifying upstream dependencies? #600
Unanswered
liangfengmic
asked this question in
Q&A
Replies: 2 comments
-
|
I'm also interested to know how to update task based on updated specs |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I think we should interact with AI in this case to provide more content and intent, example: You: I'm implementing add-dark-mode but discovered the design approach AI: Let me update design.md based on what you've learned... You: Yes AI: ✓ Updated tasks.md |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Description
I'm trying to understand the "Fluid" workflow philosophy in OpenSpec 1.0. The documentation states:
"Natural—update any artifact anytime" (https://github.com/Fission-AI/OpenSpec/blob/main/docs/migration-guide.md#whats-changing)
"During implementation, if you discover the design needs adjustment, just update the artifact and continue." (https://github.com/Fission-AI/OpenSpec/blob/main/docs/getting-started.md)
However, I'm encountering a workflow gap:
Scenario:
Problem:
Question:
I found a proposal for this exact issue at openspec/changes/add-artifact-regeneration-support/proposal.md in the repo, but it appears unimplemented (only proposal.md exists, no design/specs/tasks).
Any clarification would be greatly appreciated!
Beta Was this translation helpful? Give feedback.
All reactions