agentleFS
Sign inStart free
badgidsbadgids/Story-Film-Skills/skills/documented-creative-discovery/SKILL.md

documented-creative-discovery

Skill4 starsChanged 3 months agoApache-2.0View on GitHub

Run a decision-tree creative interview while maintaining durable Story-Film decisions, terminology, canon implications, evidence links, and open questions as the discussion progresses.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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. Very specific:

    Use decision-tree-interview, then persist the useful result rather than leaving it only in chat.

    line 10
  2. Distinctive:

    Do not duplicate entire bibles, specs, or research files.

    line 21

≈ “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

Documented Creative Discovery

Use decision-tree-interview, then persist the useful result rather than leaving it only in chat.

Maintain:

  • 00_project/creative_decisions.jsonl for DEC-### decisions
  • 00_project/production_glossary.md for project-specific production/story terms that an agent could misinterpret
  • existing canon/story-state artifacts for facts that become canon or mutable narrative state
  • 00_project/creative_production_spec.md for durable project production conventions that are not story canon
  • SRC-### and CLAIM-### when a decision depends on factual evidence
  • 00_project/decision_map.* when the effort is too large for one session

Do not duplicate entire bibles, specs, or research files. Link to the authoritative artifact and record only the decision, its concise rationale, and its consequences.

A decision record must never contain private chain-of-thought.

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