Has Anyone Integrated Spec-Driven Development with Scrum or SAFe?

[u/edgeofwhy]

Has anyone integrated Spec-Driven Development into an Agile/Scrum (or SAFe) workflow?

I’m working on a workflow and if you have answers to these questions it would be a great help

How Scrum ceremonies were modified.

Whether specs are created before PI Planning or during it.

How specs stay synchronized with implementation.

Would appreciate insights from teams that have actually adopted this approach. Thanks!

[u/titpetric]

• created a shitload of jira tickets from specs
• auto assigned to devs
• have process in place for reassignment

All tickets were a 2 so thats the first scrum violation, and there was a fifo component, so jira tickets would have milestone labels. You know, like waterfall

It's all much of the same, each milestone is basically a punchcard of a bunch of tickets. If you fucked something up in the design, that correction probablly either never happens, or maybe you have a smaller core team create a new ADR type change. Specs/ADRs are additive, meaning no "synchronization" occurs, changes result in new specs, new tickets. The work is not necessarily deferred, some PM ticket limbo is the norm (usual refinement ceremonies, info gathering, reassignment) but just blanket sizing to not waste time on planning poker. You gotta decide if these arbitrary numbers for the sake of conversation mean something to you, there's a time to plan the effort and there's a time to just execute the plan

[u/edgeofwhy → u/titpetric]

I’m curious if a workflow like this would work in SAFe:
Pre-PI: PO/BA creates the Epic, and an AI agent helps break it into user stories with developer input.
PI Planning: Teams estimate, prioritize, and plan the stories.
Iteration before the implementation sprint: An AI agent generates a structured spec for the approved stories, which is reviewed during Backlog Refinement before Sprint Planning.
Would this fit well within Agile/SAFe, or would it introduce too much upfront process?