Initial TrueGrowth source import
This commit is contained in:
14
openspec/changes/add-creative-brief-workflow/proposal.md
Normal file
14
openspec/changes/add-creative-brief-workflow/proposal.md
Normal file
@@ -0,0 +1,14 @@
|
||||
# Change: Add shared creative brief workflow
|
||||
|
||||
## Why
|
||||
The MV creator and popular video tool currently expose visual style, music mood, duration, and model controls, but they lack a structured creative intent layer. Users need lightweight professional controls for purpose/scene, directing style, narrative style, platform, audience, pacing, and avoid terms so scripts and generation prompts become more targeted.
|
||||
|
||||
## What Changes
|
||||
- Add an optional shared creative brief to existing MV and popular video records without adding a new storage entity.
|
||||
- Provide reusable creative brief presets and a compact shared editor for MV and popular video script flows.
|
||||
- Feed the brief into storyboard/script rewrite prompts and single-shot video/frame prompts.
|
||||
- Fix MV storyboard generation so initial storyboard prompts receive the selected video style and aspect ratio.
|
||||
|
||||
## Impact
|
||||
- Affected specs: `video-analyzer`, `video-mv-workflow-parity`, `video-batch-generation`
|
||||
- Affected code: workflow shared presets/prompt builders, MV creator pages/utils/types, video analyzer pages/utils/types, targeted tests
|
||||
@@ -0,0 +1,19 @@
|
||||
## ADDED Requirements
|
||||
|
||||
### Requirement: Popular Video Creative Brief
|
||||
The popular video tool SHALL persist an optional creative brief on the existing product/script configuration and use it when rewriting scripts.
|
||||
|
||||
#### Scenario: Rewrite script with creative brief
|
||||
- **WHEN** the user sets purpose/scene, directing style, narrative style, or advanced brief fields and starts AI script rewrite
|
||||
- **THEN** the rewrite prompt includes the selected brief
|
||||
- **AND** the returned script is instructed to adapt hook, selling structure, pacing, narration density, and CTA to the brief
|
||||
|
||||
#### Scenario: Choose a purpose or scene preset
|
||||
- **WHEN** the user opens the professional creative brief editor
|
||||
- **THEN** the popular video tool SHALL provide grouped purpose and scene presets such as conversion, local lifestyle, knowledge/tutorial, story/emotion, brand, and music/MV directions
|
||||
- **AND** the selected purpose or scene SHALL be persisted and included in rewrite, frame, and video generation prompts
|
||||
|
||||
#### Scenario: Open old record without brief
|
||||
- **WHEN** the user opens a record created before creative brief support
|
||||
- **THEN** the script page loads without errors
|
||||
- **AND** all creative brief fields are treated as empty defaults
|
||||
@@ -0,0 +1,14 @@
|
||||
## ADDED Requirements
|
||||
|
||||
### Requirement: Generation Prompts Inherit Creative Brief
|
||||
Single-shot and batch video generation prompts SHALL inherit the workflow creative brief when present.
|
||||
|
||||
#### Scenario: Generate shot video with creative brief
|
||||
- **GIVEN** a workflow record has a creative brief
|
||||
- **WHEN** the user generates a single shot video or starts batch video generation
|
||||
- **THEN** each video prompt includes the relevant directing, pacing, platform, audience, and avoid constraints
|
||||
|
||||
#### Scenario: Empty creative brief keeps existing behavior
|
||||
- **GIVEN** a workflow record has no creative brief
|
||||
- **WHEN** the user generates frames or videos
|
||||
- **THEN** prompt output remains compatible with the existing prompt structure
|
||||
@@ -0,0 +1,21 @@
|
||||
## ADDED Requirements
|
||||
|
||||
### Requirement: Shared Creative Brief Controls
|
||||
The system SHALL provide the same lightweight creative brief controls for the MV creator and popular video tool.
|
||||
|
||||
#### Scenario: Configure shared brief fields
|
||||
- **WHEN** the user opens the script/config area for either workflow
|
||||
- **THEN** the user can set purpose/scene, directing style, and narrative style as primary controls
|
||||
- **AND** platform, audience, pacing, and avoid terms are available as advanced controls
|
||||
|
||||
#### Scenario: Persist shared brief fields
|
||||
- **WHEN** the user changes creative brief fields in either workflow
|
||||
- **THEN** the fields are saved on the existing workflow record
|
||||
- **AND** the values are restored when the record is reopened
|
||||
|
||||
### Requirement: MV Storyboard Prompt Uses Visual Context
|
||||
The MV creator SHALL pass selected visual style and aspect ratio into initial storyboard prompt generation.
|
||||
|
||||
#### Scenario: Generate storyboard with style and ratio
|
||||
- **WHEN** the user generates an MV storyboard with selected video style or aspect ratio
|
||||
- **THEN** the storyboard prompt includes those visual constraints
|
||||
9
openspec/changes/add-creative-brief-workflow/tasks.md
Normal file
9
openspec/changes/add-creative-brief-workflow/tasks.md
Normal file
@@ -0,0 +1,9 @@
|
||||
## 1. Implementation
|
||||
- [x] 1.1 Add shared creative brief types, presets, formatter, and editor component.
|
||||
- [x] 1.2 Persist optional creative brief fields on `ProductInfo` and `MVRecord` with old-record compatibility.
|
||||
- [x] 1.3 Add the brief editor to MV and popular video script/config flows.
|
||||
- [x] 1.4 Inject creative brief context into storyboard, rewrite, frame, and video prompt builders.
|
||||
- [x] 1.5 Pass MV video style and aspect ratio into initial storyboard prompt generation.
|
||||
- [x] 1.6 Add focused unit tests for prompt builders and migration compatibility.
|
||||
- [x] 1.7 Run OpenSpec validation and targeted tests.
|
||||
- [x] 1.8 Merge purpose and scene presets into one professional creative brief control and inject it into prompt context.
|
||||
Reference in New Issue
Block a user