Marketing Foundation
Compact two-skill starter: clarify positioning and choose a lead magnet. Use Marketing Launch for the broader eight-skill go-to-market workflow.
The tunnel uses the same cards as the catalogue. Browse only as deep as needed — or load a broad bundle immediately.
SEO, Sales, Agents or another broad area → one bundle call → work.
Read-only access to published skills. Default 8, maximum 10 skills / 120,000 characters.
Compact two-skill starter: clarify positioning and choose a lead magnet. Use Marketing Launch for the broader eight-skill go-to-market workflow.
Build an evidence-led marketing plan from ICP and competition through positioning, campaigns, growth and measurement.
Diagnose architecture and context, plan agent-team responsibilities, then organize project context and session handoffs. Memory and cost-runtime reviews remain outside this pack.
Review the journey from landing page and lead capture through registration, first value and transparent upgrades.
Plan a campaign, draft its channel content and review the work against actual brand guidance.
Prioritize an editorial roadmap and plan how to launch and distribute it across suitable channels.
Understand customer needs, compare competitors and plan a community around real member value.
Choose a relevant lead magnet, then draft a permission-based nurture journey with entry, suppression and exit rules.
Define the API contract, then plan how to observe its latency, failures and retries. Guidance and checklist; no production changes.
Profile a dataset, choose and interpret statistical methods, then validate calculations and conclusions before sharing.
Develop a short-film idea into a logline, treatment, scene list and revision plan.
--- name: short-film-development description: "Develop short stories and short films from raw ideas into loglines, premises, themes, character engines, conflict, structure, treatments, scene lists, prose plans, and revision plans for cinematic AI production." --- # short-film-development ## When to use - A user has a raw idea, image, premise, theme, genre, character, or mood and wants a short-film concept. - The user asks for loglines, treatments, outlines, short-story plans, character conflict, theme, acts, or a revision plan. - The next downstream task is screenplay, shot list, visual bible, image prompts, or video prompts. ## When not to use - The user already has locked script pages and only needs shot extraction. - The task is only model-specific prompt translation. - The user wants legal clearance, financing, casting, or production scheduling. ## Required inputs - Raw idea or constraint - Target length or runtime range - Genre/tone/audience if known - Any required characters, locations, or production limits ## Optional inputs - Reference films or style anchors - Theme or emotional promise - Available AI models or output format - Continuity bible entries ## Workflow 1. Clarify the creative intent layer: story engine, theme, protagonist desire, emotional wound, obstacle, stakes, point of view if prose, and audience experience. 2. Generate 3 to 5 divergent concept routes when the idea is early; select or recommend one based on specificity, feasibility, and cinematic promise. 3. Write a logline with protagonist, goal, obstacle, stakes, and irony or pressure. 4. Expand into premise, theme statement, character engine, central conflict, world rules, and ending direction. 5. Choose a compact structure: unity-of-effect short story, Fichtean crisis curve, single turning point, three-beat micro-arc, circular reveal, escalation spiral, or procedural countdown. 6. Create a scene list where every scene has dramatic purpose, visual purpose, emotional turn, and continuity needs. 7. Produce a revision plan that strengthens causality, compresses exposition, and removes unfilmable abstraction. ## Decision logic - If the idea is vague, run idea intake before writing. - If the concept is visually strong but narratively thin, build the character want/need conflict first. - If runtime is under 3 minutes, prefer one location, one core conflict, and one major turn. - If the user wants prompts soon, preserve image/video-ready visual anchors in every scene. ## Output formats - Logline - Premise sheet - Theme and audience experience brief - Character conflict map - Short-story plan - Short treatment - Scene list - Revision plan - Downstream handoff brief ## Quality checks - The logline contains a filmable conflict, not just a mood. - Each scene changes story state or emotional state. - The ending answers the opening tension. - The concept includes reusable visual anchors for continuity and prompting. - The treatment separates what the audience sees/hears from backstory. ## Anti-patterns - Abstract themes with no visible action - Too many locations for a short runtime - Worldbuilding that does not affect choices - A protagonist who only observes - Prompt-ready imagery that contradicts the story tone ## Exit criteria - A concise concept package exists and can feed screenplay, shot list, bible, or prompt generation without re-interviewing the user. ## Supporting files Read only the supporting file needed for the active task: - `references/story_development_workflow.md` - `references/ai_storytelling_workflow.md` - `references/screenplay_structure.md` - `references/continuity_handoff.md` - `templates/idea_intake.md` - `templates/logline.md` - `templates/short_film_treatment.md` - `templates/short_story_plan.md` - `templates/story_revision_audit.md`
Develop a short-film idea into a logline, treatment, scene list and revision plan.
The complete original workflow, with source attribution and the limitations below.
Confirm the task, check actual dependencies, then apply the relevant original instructions within authorized scope.
Idea, runtime, genre, audience and production constraints.
Published after an obvious-danger screen under the user-requested policy, not a functional test. Supporting files required conditionally by the original are not supplied: references/story_development_workflow.md, references/ai_storytelling_workflow.md, references/screenplay_structure.md, references/continuity_handoff.md, templates/idea_intake.md, templates/logline.md, templates/short_film_treatment.md, templates/short_story_plan.md, templates/story_revision_audit.md. Related model-adaptation/continuity handoffs must be available for the actual task; loading this source does not load them. No media generation, model-capability verification or code execution was performed. Treat named-model parameters as unknown until checked and use authorized references/assets.
Use Short Film Development for [TASK]. Ask for missing inputs: Idea, runtime, genre, audience and production constraints. Check the declared dependencies and limitations before execution. Return the original output structure with known facts, assumptions and unresolved requirements separated.
Claiming that unavailable source dependencies are bundled or that generated outputs, integrations or model behavior have been tested. Actual media generation without a separately available authorized tool.
M11 added German routing, task inputs and explicit source-package limitations; the original author remains separate from M11 curation. Published after an obvious-danger screen under the user-requested policy, not a functional test. Supporting files required conditionally by the original are not supplied: references/story_development_workflow.md, references/ai_storytelling_workflow.md, references/screenplay_structure.md, references/continuity_handoff.md, templates/idea_intake.md, templates/logline.md, templates/short_film_treatment.md, templates/short_story_plan.md, templates/story_revision_audit.md. Related model-adaptation/continuity handoffs must be available for the actual task; loading this source does not load them. No media generation, model-capability verification or code execution was performed. Treat named-model parameters as unknown until checked and use authorized references/assets.
MIT License Copyright (c) 2026 0xhughs Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Copy the text below, then paste it into your chat.