start-goal

name	start-goal
description	Use when the user says "стартуем цель", "запусти цель", "start goal", "goal:", asks to turn a rough objective into a Codex /goal run, or wants an agent to interview/brainstorm first and then execute autonomously.

Start Goal

Turn a rough user objective into an executable Codex goal with enough context, acceptance criteria, and verification to run safely.

Core Rule

Do not start /goal from a vague request. First convert it into a goal brief with measurable Done when criteria. If the request is creative, product, website, feature, strategy, or behavior-shaping work, use the brainstorming skill before execution.

Workflow

1. Name the assumption

   • Restate the objective in one sentence.
   • State whether this is likely discovery, analysis, implementation, or maintenance.
   • Define 1-3 verifiable completion criteria before doing work.

2. Choose intake depth

   • If enough context exists: write the goal brief directly.
   • If key info is missing: ask one concise question at a time.
   • If the objective is broad or creative: invoke brainstorming and complete its approval flow before implementation.
   • If the objective is messy client/product requirements: invoke project-manager before brainstorming.

3. Collect minimum parameters

   • Objective
   • Project/context
   • Target audience/user
   • Inputs/assets/sources
   • Constraints and exclusions
   • Deliverables
   • Verification commands/checks
   • Stop conditions and escalation points

4. Produce the goal brief

   • Use the template in references/goal-templates.md.
   • Include a Done when block with commands, files, browser checks, or concrete review criteria.
   • Include Do not boundaries for irreversible, paid, production, or user-owned actions.

5. Confirm before long autonomous execution

   • For substantial work, show the brief and ask for approval.
   • For small safe tasks, proceed after stating the brief.

6. Run or hand off

   • If the user explicitly wants Codex Goals and the environment supports it, start with: /goal Use goal to execute the approved goal brief. Continue until all Done when criteria pass.
   • If /goal is unavailable in the current channel, execute the brief manually using the same criteria.

7. Finish with evidence

   • Report changed files/artifacts.
   • Report verification commands and results.
   • If incomplete, report blocker, attempts, and the next smallest action.

Quick Trigger Example

User: "стартуем цель - GAP анализ для нового сайта по продаже арматуры"

Response shape:

• Assumption: "Нужно сравнить будущий сайт с конкурентами/ожиданиями рынка и найти gaps для лендинга/каталога арматуры."
• Intake: ask for region, product type, competitors, target buyer, or use known project context if available.
• If missing positioning/design decisions: use brainstorming.
• Goal brief: research sources, GAP matrix, prioritized recommendations, page/section implications, verification checklist.

Reference

Read references/goal-templates.md when drafting a goal brief, examples, or parameter checklist.