mirror of
https://github.com/mikeyobrien/ralph-orchestrator.git
synced 2026-04-25 07:05:57 +03:00
[GH-ISSUE #162] [Feature]: Switch / support the OpenSpec SDD standard #62
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ralph-orchestrator#62
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @matbgn on GitHub (Feb 7, 2026).
Original GitHub issue: https://github.com/mikeyobrien/ralph-orchestrator/issues/162
Use case
Ensure we follow standards instead of reinventing the wheel, ONLY if it's realistic of course.
Proposed solution
Is it feasible / thinkable / wishable to switch to this emerging industry standard?
https://github.com/Fission-AI/OpenSpec/
Area
CLI
Backend(s) impacted
All
Alternatives considered
No response
Additional context
No response
@mikeyobrien commented on GitHub (Feb 7, 2026):
This is not reinvented. This is what we use internally at Amazon.
See: https://github.com/strands-agents/agent-sop
That said, I don't mind adding this as an option.
@matbgn commented on GitHub (Feb 7, 2026):
My apologies, please ignore this request. I don't won't to add overengineering, just wanted to contribute to the sustainability of this just amazing project. But it makes no sense here as everything is already polished on that side.
Thank you for the enlightenment. 🙏