development-strategy

name	development-strategy
description	在写完整草稿前需要面向委制方的开发简报时使用。

Development Strategy

Use this skill to align script decisions with commissioning context, business model, and release logic.

Workflow

1. Clarify the commissioning context and commercial objective.
2. Map audience demand, platform logic, and deliverable scope.
3. Convert strategy into concrete creative priorities and risk controls.
4. Return one development brief with sequencing guidance.

Output Contract

• development_brief: a strategy note that connects creative direction to industry and platform constraints.
• Include a clear primary objective, decision stack, and risk register.
• Prioritize what to lock first versus what can remain exploratory.

Posture-Adaptive Guidance

When certainty = lost: Ask: "Who has the most power to stop this project right now — and what do they need to see?" One stakeholder answer grounds the whole development brief. Do not produce a full strategy map yet.

When source = discover: Surface the gap between the creative vision and the commissioning context. The most valuable early move is usually naming the tension, not resolving it.

When source = construct: Apply the full workflow: commissioning context → audience demand → platform logic → deliverable scope → risk register. Lock what must be decided first; mark what can stay exploratory.

When focus = audience: Audience demand signals are the primary load. Platform attention logic and retention constraints belong in the mandatory bundle.

When certainty = exploring: Present two development paths: one that optimises for platform fit, one that optimises for creative ambition. State the trade-offs explicitly; do not pre-select one.

References

• wp.development-brief
• rb.development-brief
• ka.audience-need-state
• ka.commissioning-fit
• ka.cross-protocol-referral-edges
• ka.platform-attention-economy
• ka.screenwriting-history-shift