{
 "schema_version": 1,
 "generated": "2026-10-20",
 "id": "jtydhr88-screenwriting-skills--keep-screenplay-project-state-across-sessions",
 "repo": "jtydhr88/screenwriting-skills",
 "repo_url": "https://github.com/jtydhr88/screenwriting-skills",
 "repo_slug": "jtydhr88-screenwriting-skills",
 "title": "Track a screenplay project's stage across sessions",
 "page_title": "How to track a screenplay project's stage across sessions with Screenwriting Skills",
 "summary": "Use the workflow orchestrator and a story bible file to keep your screenplay's stage and decisions between chats.",
 "who": "A writer who works on a script over many sessions and loses track of which stage they reached and which decisions are settled.",
 "problem": "Without a shared record, each new session restarts from memory, and stage deliverables and open decisions get lost.",
 "outcome": "A story bible file that records project state, plus a stage check that says where to pick up next time.",
 "steps": [
  "Run `/plugin marketplace add jtydhr88/screenwriting-skills` in Claude Code.",
  "Run `/plugin install screenwriting@screenwriting-skills` in Claude Code.",
  "Ask the workflow skill to set up a project and create a story bible file in your project folder.",
  "At the end of each session, ask the agent to update the story bible with the current stage, open questions and next steps."
 ],
 "agent_prompt": "Using the screenwriting-skills repo (sw-workflow), set up a project for <project name> and create a story bible file that tracks the current stage, settled decisions and open questions. Verify at the start of each new session that the agent reads the file and states the current stage before writing anything.",
 "agents": [
  "claude-code",
  "codex"
 ],
 "difficulty": "Intermediate",
 "time": "15 minutes",
 "basis": "readme",
 "caveat": "The workflow's exit checks are advisory, so the agent will flag missing deliverables but will not block you from moving on.",
 "category": "Content",
 "tags": [
  "Content"
 ],
 "lang": "python",
 "requirements": [
  "Claude Code or OpenAI Codex installed",
  "Git available if you use the clone-and-copy install route",
  "Your series outline, script pages or story notes as text"
 ],
 "risk": "none",
 "seen_in_the_wild": false,
 "mentioned_publicly": false,
 "risks": [],
 "best": false,
 "score": 0.7,
 "evidence": [],
 "url": "https://dedupedai.com/use-cases/jtydhr88-screenwriting-skills/keep-screenplay-project-state-across-sessions/",
 "md": "https://dedupedai.com/use-cases/jtydhr88-screenwriting-skills/keep-screenplay-project-state-across-sessions/index.md",
 "disclaimer": "Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked \"Seen in the wild\", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email hello@dedupedai.com and we will look at it promptly.",
 "api": "https://dedupedai.com/api/v1/usecases/jtydhr88-screenwriting-skills--keep-screenplay-project-state-across-sessions.json",
 "api_version": "v1"
}