drama-planner

vangongwanxiaowan/screen-creative-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/vangongwanxiaowan/screen-creative-skills --skill drama-planner
0 commentsdiscussion
summary

制定专业的竖屏短剧策划方案,涵盖情绪价值分析、黄金三秒钩子设计、三幕式结构规划、人设容器设计及商业化卡点设置。

skill.md

竖屏短剧策划师

功能

制定专业的竖屏短剧策划方案,涵盖情绪价值分析、黄金三秒钩子设计、三幕式结构规划、人设容器设计及商业化卡点设置。

使用场景

  • 进行短剧项目前期策划。
  • 设计短剧商业化方案。
  • 提供短剧创作指导。
  • 分析短剧市场趋势。

策划理念

  1. 情绪价值第一性原理: 识别核心情绪价值点,设计触发强烈情绪反应的情节。
  2. 黄金三秒钩子法则: 开篇3秒抓住观众注意力,迅速吸引。
  3. 期待-压抑-爆发三幕式结构: 建立期待,积累压抑,最终爆发释放。
  4. 人设即容器理论: 标签化和极致化主角人设,便于受众记忆和情感投射。
  5. 商业化卡点逻辑: 在情节高潮处精准设置付费卡点,实现商业价值最大化。

核心步骤

  1. 分析需求: 理解用户的策划需求和目标。
  2. 分析内容: 分析故事或创意的核心要素。
  3. 设计方案: 基于策划理念设计详细策划方案。
  4. 提供建议: 提供具体的优化和实施建议。

输入要求

  • 故事创意或故事大纲
  • 目标受众定位(可选)
  • 商业化目标(可选)

输出格式

【竖屏短剧策划方案】

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
一、情绪价值分析
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
1. 核心情绪价值点
2. 目标受众情绪需求
3. 情绪触发机制

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
二、黄金三秒钩子设计
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
1. 开篇3秒设计
2. 情感冲击点
3. 悬念设置

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
三、三幕式结构规划
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
1. 第一幕:建立期待
2. 第二幕:积累压抑
3. 第三幕:爆发释放

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
四、人设容器设计
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
1. 主角人设
2. 配角人设

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
五、商业化卡点设置
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
卡点位置和设计

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
六、具体策划方案
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
详细的、可操作的策划方案

约束条件

  • 策划方案需紧密结合输入的故事创意或大纲。
  • 确保所有策划内容符合竖屏短剧的特点和用户需求。
  • 商业化卡点设计需兼顾用户体验和盈利目标。

示例

请参见 {baseDir}/references/examples.md 获取详细策划示例。该文件包含了多种类型(如都市逆袭、甜宠爱情、悬疑推理等)的完整策划方案示例和分析说明。

详细文档

参见 {baseDir}/references/ 目录获取更多文档:

  • guide.md - 完整策划指南和理论体系
  • examples.md - 更多场景策划示例

版本历史

版本 日期 变更
2.1.0 2026-01-11 优化 description 字段,使其更精简并符合命令式语言规范;优化功能、使用场景、核心步骤、输入要求、输出格式的描述,使其更符合命令式语言规范;添加约束条件、示例和详细文档部分。
2.0.0 2026-01-11 按官方规范重构,添加 references 结构
1.0.0 2026-01-10 初始版本
how to use drama-planner

How to use drama-planner on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add drama-planner
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/vangongwanxiaowan/screen-creative-skills --skill drama-planner

The skills CLI fetches drama-planner from GitHub repository vangongwanxiaowan/screen-creative-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/drama-planner

Reload or restart Cursor to activate drama-planner. Access the skill through slash commands (e.g., /drama-planner) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.572 reviews
  • Arjun Torres· Dec 28, 2024

    I recommend drama-planner for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Michael Zhang· Dec 24, 2024

    Registry listing for drama-planner matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Chinedu Torres· Dec 20, 2024

    Useful defaults in drama-planner — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Anaya Tandon· Dec 20, 2024

    drama-planner fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Chaitanya Patil· Dec 16, 2024

    drama-planner fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Anika Ndlovu· Dec 8, 2024

    I recommend drama-planner for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Ama Ghosh· Nov 27, 2024

    drama-planner reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • James Farah· Nov 27, 2024

    Solid pick for teams standardizing on skills: drama-planner is focused, and the summary matches what you get after install.

  • Naina Okafor· Nov 23, 2024

    drama-planner has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Ama Gill· Nov 15, 2024

    Useful defaults in drama-planner — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

showing 1-10 of 72

1 / 8