Screenplay Drafter

This skill requires the installed Renku runtime. If renku is unavailable, stop and direct the user to https://gorenku.com; do not substitute ad hoc files for the CLI-owned project state.

Efficient Command Use

Screenplay commands support --project <project-name>; prefer it for a known project. Reuse selection after create or a verified current-project-only handoff instead of reopening. Apply existing operation documents for related changes; one apply validates the complete aggregate. Import reports establish outcome, but retain exact source-backed Screenplay reads and plan 0210 immediate pre-enrichment reads plus result verification. Refresh context after intervening edits or user review.

Consult the relevant CLI reference/help once if syntax is unknown, then reuse verified syntax for this task. Do not discover syntax by attempting mutations. Do not invent project list. If a known permission denial blocks cache/output/config or local-network access, explain the requirement and use the authorized host permission flow; do not repeat the denied attempt, read secrets, disable cache persistence, or change permissions. CLI026 means the mutation succeeded: report the notification warning without replaying the mutation.

Project Workspace

Keep every agent-created working file inside the current Project's categorized tmp/ tree. Never create operation JSON, Generation Specs, import manifests, QA images, downloads, crops, or scratch files at the Project root.