Dedicated Screenplay / Scenario workspace — what should a real screenwriting workflow look like?

[qnbs]

Why this exists

Issue #347 identifies the need for a dedicated Scenario / Screenplay workspace. This Discussion is the product and UX exploration space for that implementation goal; it does not replace the Issue's acceptance or sequencing authority.

Current state

WorldScript Studio already has shared project concepts for characters, worlds, story structure, scenes, notes, storyboard/plot-board work, manuscript editing, and export. The open product question is how a screenplay workflow should compose those capabilities without fragmenting the common writing model.

Product decision space

We can explore a dedicated workspace, a project type, or a view preset. The scope may include characters, worlds, pitch, logline, synopsis, story structure, scenes, notes, storyboard, and manuscript views. Fountain and Final Draft interoperability are open questions, not commitments. Please distinguish an MVP screenplay workflow from advanced production-suite tooling.

What #347 already tracks technically

#347 remains the implementation and acceptance tracker for the Scenario / Screenplay workspace. Technical decisions, implementation slices, tests, roadmap admission, and acceptance criteria belong there.

Role perspectives

Role-perspective note: The viewpoints below are maintainer-curated, AI-assisted design lenses. They are not separate community members, votes, or evidence of consensus.

• 🎬 Screenwriter: workflow depth, scene structure, formatting, and production-specific needs.
• ✍️ Novelist: avoid fragmenting shared writing concepts or making the general writing model screenplay-only.
• ♿ Accessibility: keyboard and focus behavior, structured navigation, readable hierarchy, and non-pointer workflows.
• 🧭 Maintainer: keep the MVP bounded and separate it from specialist production-suite scope.

Questions for the community

• Would you prefer a dedicated workspace, a project type, or a configurable view preset?
• Which screenplay tasks must be present in the MVP?
• Which shared project concepts should remain identical across novel and screenplay workflows?
• Which import/export formats would be useful enough to justify first-class support?
• What would make advanced screenplay tooling worth its maintenance cost?

Relationship to implementation

This Discussion gathers product and UX input only. It does not change #347's priority, roadmap admission, acceptance criteria, implementation authority, or execution sequencing.