メニュー
Create landing-page-ready product handoff using Mode-C contract gates (opportunity selection, scope boundary, evidence traceability) and write output for marketing consumption.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Design, run, and audit Stage3 Iterate on product capability for OperatorOne. Use when asked to convert Stage1 metrics and Stage2 feedback priorities into experiment backlogs, rollout plans, policy-driven decisions (ship/iterate/rollback/park), learning logs, and cross-team iteration handoffs; or when asked to bootstrap Stage3 contracts/config, enforce guardrails, and verify strict reproducibility.
Implement and operate Stage2 Process feedback capability for OperatorOne. Use when asked to build, run, audit, or deliver feedback processing from ingestion through prioritization and closed-loop tracking; generate Stage2 feedback scoreboards/alerts/weekly snapshots; create operations_to_product/marketing/sales handoffs; enforce strict reproducibility; or migrate from simulated feedback adapters to live sources.
End-to-end Stage3 conversion execution for op1_sales. Use when asked to convert early customers, move leads from interest/discovery into pilot and paid start, generate close-motion playbooks, track pilot onboarding and TTFV, process conversion signals (commitment/paid/lost), produce conversion scoreboards, or run reproducible conversion audits.
End-to-end Stage2 send outreach pipeline for op1_sales. Use when asked to send outreach, run follow-up sequences, generate outreach dispatch packs, approval-gated dispatch batches, process outreach replies, enforce suppression/frequency controls, or roll up outreach outcomes into handoffs/sales_to_operations.json.
Implement and operate Stage1 tracking for OperatorOne operations (traffic, signups, revenue). Use when asked to build, run, audit, or deliver this capability; bootstrap contracts/adapters; generate Stage1 scoreboards and weekly KPI snapshots; enforce data quality and reproducibility; or migrate from simulated signals to live analytics/billing sources.
Build and refresh Stage1 prospect-identification outputs for op1_sales. Use when asked to identify prospects, rank ICP segments, show top prospects, or generate evidence-backed lead queues from OperatorOne handoff data (marketing_to_sales, opportunity_records, reddit_signals).
| name | op1-product-landing-handoff |
| description | Create landing-page-ready product handoff using Mode-C contract gates (opportunity selection, scope boundary, evidence traceability) and write output for marketing consumption. |
Use this skill when the request is to produce a landing-ready handoff from Stage1/2/3 artifacts with explicit quality gates.
research/stage1_idea_discovery/opportunity_records.jsonresearch/stage2_idea_screening/decision_log.json, research/stage3_mvp_scope/project_blueprint.jsonresearch/build_deploy_v1/project_spec.jsonPreferred one-command path:
./scripts/run_create_landing_pages_v1.sh
This will:
project_spec + page_spec).../../handoffs/product_to_marketing.json.research/landing_v1/landing_package.jsonresearch/landing_v1/landing_contract_test.latest.jsonresearch/landing_v1/landing_semantic_test.latest.jsonresearch/landing_v1/build_inputs/project_spec.jsonresearch/landing_v1/build_inputs/page_spec.json../../handoffs/product_to_marketing.jsonpage_mode=landing.out_of_scope boundary.