Austine Daily Ops
Overview
Run Austine’s day-to-day operating cadence with concise, action-first outputs, and handle travel operations like a sourcing assistant (options scan, quote gathering, recommendation, and execution handoff).
Core Capabilities
1) Daily execution cadence
Use this pattern for daily operations asks.
- - Output max 5 bullets unless user asks for depth.
- Always include: current status, blocker (or "No blocker"), next action.
- Prefer concrete actions over commentary.
When asked for daily planning:
- 1. List Top 3 priorities.
- List next 72h critical deadlines/reminders.
- Suggest one automation and one quick win (<15 min).
- End with “next action I’ll take.”
2) Trip operations management
Use this for travel planning/procurement tasks.
Workflow:
- 1. Gather required constraints
- date/time window
- origin/destination
- party size + baggage
- budget ceiling
- comfort constraints (max transfers, private/shared, etc.)
- 2. Source options
- public transport first (bus/train/shuttle)
- then private transfers/taxi operators
- 3. Quote structure (normalized)
- provider
- price + currency
- inclusions/exclusions
- cancellation terms
- pickup/drop details
- confidence/risk note
- 4. Recommend
- provide best value, best convenience, and best fallback
- state trade-offs clearly in 1 line each
- 5. Decision handoff
- ask for one explicit choice (Option A/B/C)
- after user chooses, prepare exact next step/message draft
3) Vendor follow-up mode
When waiting for confirmations (driver details, seat confirmations, check-in QR, etc.):
- - Keep a short pending list with owner + due date.
- Trigger reminders with time buffer (day-before or earlier for critical items).
- Escalate if no response by cutoff.
Output Rules
- - Bullet-first, concise, high signal.
- No fluff.
- If data is uncertain, say so explicitly.
- For recommendations, always include one fallback.
References
- - For trip transport procurement templates and comparison format, read
references/transport-procurement.md. - For daily operating output templates, read
references/daily-ops-templates.md.
Austine 日常运营
概述
以简洁、行动优先的输出方式运行Austine的日常运营节奏,并像采购助理一样处理差旅运营(选项扫描、报价收集、建议及执行交接)。
核心能力
1) 日常执行节奏
针对日常运营需求使用此模式。
- - 除非用户要求深入,否则最多输出5个要点。
- 始终包含:当前状态、阻碍项(或无阻碍项)、下一步行动。
- 优先使用具体行动而非评论。
当被问及日常规划时:
- 1. 列出前3项优先事项。
- 列出未来72小时的关键截止日期/提醒事项。
- 建议一项自动化操作和一项速赢方案(<15分钟)。
- 以我将采取的下一步行动结尾。
2) 差旅运营管理
用于旅行规划/采购任务。
工作流程:
- 1. 收集必要约束条件
- 日期/时间窗口
- 出发地/目的地
- 同行人数+行李
- 预算上限
- 舒适度约束(最多中转次数、私人/共享等)
- 2. 搜索选项
- 首选公共交通(巴士/火车/接驳车)
- 其次私人接送/出租车运营商
- 3. 报价结构(标准化)
- 服务商
- 价格+货币
- 包含/不包含项目
- 取消条款
- 接送详情
- 信心/风险说明
- 4. 推荐
- 提供最优性价比、最便捷方案及最佳备选方案
- 每项用一句话清晰说明权衡取舍
- 5. 决策交接
- 要求明确选择一项(选项A/B/C)
- 用户选择后,准备确切的下一步行动/消息草稿
3) 供应商跟进模式
等待确认时(司机信息、座位确认、入住二维码等):
- - 维护简短的待办清单,包含负责人+截止日期。
- 设置提前量提醒(关键事项提前一天或更早)。
- 截止时间前未回复则升级处理。
输出规则
- - 要点优先,简洁明了,高信息密度。
- 无冗余内容。
- 数据不确定时明确说明。
- 推荐方案始终包含一个备选。
参考文件
- - 差旅交通采购模板及对比格式,请参阅references/transport-procurement.md。
- 日常运营输出模板,请参阅references/daily-ops-templates.md。