agentleFS
Sign inStart free
badgidsbadgids/Story-Film-Skills/skills/creative-production-spec/SKILL.md

creative-production-spec

Skill4 starsChanged 3 months agoApache-2.0View on GitHub

Synthesize the current Story-Film conversation and project state into a durable creative and production specification without reopening decisions that have already been settled.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read existing brief, canon, bibles, decisions, evidence, resource constraints, production capabilities, and requested delivery scope.

    line 12
  2. Distinctive:

    Do not interview unless the existing material contains a true contradiction that prevents faithful synthesis.

    line 13
  3. Very specific:

    Write 00_project/creative_production_spec.md using the reference structure.

    line 14
  4. Distinctive:

    Run project validation before treating the spec as ready for work-unit decomposition.

    line 18

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Creative Production Spec

Read ../../references/CREATIVE_PRODUCTION_SPEC.md.

  1. Read existing brief, canon, bibles, decisions, evidence, resource constraints, production capabilities, and requested delivery scope.
  2. Do not interview unless the existing material contains a true contradiction that prevents faithful synthesis.
  3. Write 00_project/creative_production_spec.md using the reference structure.
  4. Preserve the project's vocabulary and stable IDs.
  5. State acceptance in terms a human or validator can observe in the story, image, audio, video, film, document, campaign, or release package.
  6. Distinguish locked requirements from preferences and deferred decisions. Put project-specific naming, prompt formatting, generation, review, handoff, and delivery rules under Project Production Conventions; do not add them to story canon.
  7. Run project validation before treating the spec as ready for work-unit decomposition.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free