القائمة
Use when edit_blueprint.yaml and selects_candidates.yaml are ready and the user asks to compile the rough cut, generate timeline.json, or apply a review patch.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
MUST USE when the user asks to crop, reframe, trim, or improve composition of still photos, especially selected event photos, album photos, portraits, speakers, panels, workshops, or group photos. Use after photo selection or correction when the task is composition improvement rather than selecting images.
MUST USE when the user provides a photo ZIP, photo folder, or still-image event material and asks for photo selection, album selection, highlights, digest photos, curation, or quality filtering. Use this instead of analyze-footage when the source is primarily still photos and the requested work is selecting images rather than editing or video planning.
Use when timeline.json exists and the user asks to review the rough cut, critique the edit, or generate review_report.yaml and review_patch.json.
Use after changing prompts, skills, the compiler, or editorial policies — or when the user asks to measure edit quality, run regression evals, check agreement with approved edits, or says '評価して', '一致率を測って', 'eval を回して'. Compares agent output against human-approved golden projects.
MUST USE when starting a new video project, when the user provides footage and asks to edit/create a video, or when 01_intent/creative_brief.yaml does not yet exist. This skill interviews the user to understand their intent before any editing begins. Never skip this step.
MUST USE when the user is setting up this project for the first time, when dependencies are missing, API keys are not configured, or when 'npm run demo' fails. Triggers on: 'セットアップ', '環境構築', 'setup', 'install', 'API key', 'ffmpeg not found', 'GEMINI_API_KEY', 'cannot find module'.
| name | compile-timeline |
| description | Use when edit_blueprint.yaml and selects_candidates.yaml are ready and the user asks to compile the rough cut, generate timeline.json, or apply a review patch. |
| metadata | {"filePattern":["**/05_timeline/timeline.json","**/05_timeline/preview-manifest.json","**/05_timeline/adjacency_analysis.json"],"bashPattern":["compile-timeline"]} |
creative_brief.yaml, selects_candidates.yaml, edit_blueprint.yaml が揃っているとき。scripts/compile-timeline.ts は compile 前後で scripts/validate-schemas.ts 相当の gate を見る。01_intent/unresolved_blockers.yaml に status: blocker があると compile gate が落ちる。--fps <num> を明示する。npx tsx scripts/compile-timeline.ts projects/<project> --fps 30
npx tsx scripts/compile-timeline.ts projects/<project> --patch projects/<project>/06_review/review_patch.json --fps 30
timeline.json、preview-manifest.json、必要なら adjacency_analysis.json を確認する。05_timeline/timeline.json05_timeline/preview-manifest.json05_timeline/adjacency_analysis.json ただし active editing skills による transition 解析が走った場合scripts/compile-timeline.ts の createdAt は 01_intent/creative_brief.yaml.created_at から決まる。timeline.json を上書きし、同時に preview-manifest.json も再生成する。adjacency_analysis.json は debug / explanation 用 artifact。常に生成されるわけではない。