菜单
Use when selects_candidates.yaml exists and the user asks to design structure, build an edit blueprint, or create 04_plan/edit_blueprint.yaml.
用 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 | build-blueprint |
| description | Use when selects_candidates.yaml exists and the user asks to design structure, build an edit blueprint, or create 04_plan/edit_blueprint.yaml. |
| metadata | {"filePattern":["**/04_plan/edit_blueprint.yaml","**/04_plan/uncertainty_register.yaml"],"bashPattern":[]} |
04_plan/selects_candidates.yaml があり、rough cut 前の設計を固めるとき。schemas/edit-blueprint.schema.json と schemas/uncertainty-register.schema.json を守ること。runtime/commands/blueprint.ts の narrative loop に従うこと。
frame → read → draft → evaluate → confirm → promotecreative_brief.yaml, unresolved_blockers.yaml, selects_candidates.yaml, 任意で STYLE.md。full か collaborative かを決める。04_plan/edit_blueprint.yaml を作る。
必須の核は sequence_goals, beats, pacing, music_policy, dialogue_policy, transition_policy, ending_policy, rejection_rules。beats[].target_duration_frames と required_roles を明確にし、候補素材との対応が読めるようにする。caption_policy, timeline_order, duration_policy, quality_targets, trim_policy, active_editing_skills も書く。04_plan/uncertainty_register.yaml を作る。
各 uncertainty は id, type, question, status, evidence, alternatives, escalation_required を持つ。collaborative の場合は beat proposal と pacing を readback し、pacing.confirmed_preferences を入れる。04_plan/edit_blueprint.yaml04_plan/uncertainty_register.yamluncertainty_register.yaml の status: blocker は planning 上の blocker。compile gate の hard stop は unresolved_blockers.yaml 側で管理される。hero, support, transition, texture, dialogue の enum に合わせる。timeline_order を省略した場合は schema default は editorial。chronological にしたいときだけ明示する。