Back to Details

gravitas-highstakes

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

GRAVITAS High-Stakes Skill

GRAVITAS High-Stakes Skill

For Tier-2 actions (hard-to-reverse, high-stakes), follow this skill in addition to the standard GRAVITAS cognitive loop. This skill enforces explicit user checkpoints.
对于 Tier-2 操作（难以逆转、高风险），除标准 GRAVITAS 认知循环外，还必须遵循此 skill。此 skill 强制要求设置明确的用户检查点。

Steps

步骤

1. State the Change and Tier Classification

1. 说明变更内容与 Tier 分类

Before doing anything, explicitly state:
  • What you plan to change (specific files, tables, configs)
  • Why this is Tier 2 (what makes it hard to reverse)
  • What could go wrong
Format:
This is a Tier-2 action because: [reason]
Plan:
  1. [specific step]
  2. [specific step]
  ...
Risk: [what could break]
在执行任何操作前，明确说明：
  • 变更内容：你计划更改什么（具体文件、表、config）
  • Tier 2 原因：是什么使该操作难以逆转
  • 潜在问题：可能出现什么故障
格式：
This is a Tier-2 action because: [reason]
Plan:
  1. [specific step]
  2. [specific step]
  ...
Risk: [what could break]

2. Present the Plan + Adversarial Critique

2. 提交计划与对抗性审查

Run the full Pillar 2 process:
  • Write the numbered plan
  • Run the adversarial critique (separate reasoning pass)
  • Revise the plan based on critique
  • Present the revised plan to the user
执行完整的 Pillar 2 流程：
  • 编写编号计划
  • 执行对抗性审查（独立推理过程）
  • 根据审查结果修订计划
  • 向用户提交修订后的计划

3. Dry Run (if available)

3. 试运行（如果可用）

If a dry-run, lint, test, or validation command is available for this type of change, run it now:
undefined
如果此类变更可使用 dry-run、lint、test 或 validation 命令，请立即运行：
undefined

turbo — auto-approved, no user confirmation needed for this step

turbo — auto-approved, no user confirmation needed for this step


Examples:
- Database migration: `--dry-run` flag
- Config change: schema validation
- Code change: type check + lint
- Deployment: preview environment

示例：
- 数据库迁移：`--dry-run` flag
- Config 变更：schema validation
- 代码变更：type check + lint
- 部署：preview environment

4. STOP — Wait for Explicit User Confirmation

4. 停止——等待用户明确确认

Do not execute the plan yet. Present the plan and ask for confirmation:
I've completed the reconnaissance, plan, and adversarial critique.
This is a Tier-2 (irreversible/high-stakes) action.

[Show the plan]

Do you want me to proceed with this plan? Please confirm explicitly.
Wait for the user's response. Do not proceed until they confirm.
此时不要执行计划。 展示计划并请求用户确认：
I've completed the reconnaissance, plan, and adversarial critique.
This is a Tier-2 (irreversible/high-stakes) action.

[Show the plan]

Do you want me to proceed with this plan? Please confirm explicitly.
等待用户回复。在用户确认前不得继续执行。

5. Execute the Confirmed Plan

5. 执行已确认的计划

Only after explicit confirmation:
  1. Execute each step in the plan
  2. After each step, verify it succeeded
  3. If any step fails, stop immediately — do not continue with the plan
只有在获得明确确认后才可执行：
  1. 执行计划中的每个步骤
  2. 每个步骤完成后，验证其是否成功
  3. 如果任何步骤失败，立即停止——不要继续执行计划

6. Re-Verify After Execution

6. 执行后重新验证

After all steps complete:
  1. Run any available post-change verification
  2. Re-read the changed files to confirm edits landed
  3. If applicable, run the full test suite
Report back with:
  • What was changed
  • Evidence it's working
  • Any concerns or follow-ups
所有步骤完成后：
  1. 运行所有可用的变更后验证
  2. 重新读取已更改的文件，确认修改已生效
  3. 如有必要，运行完整 test suite
向用户报告：
  • 变更了什么
  • 证明其正常工作的证据
  • 任何问题或后续事项

Abort Conditions

中止条件

Stop the skill and report to the user if:
  • A dry-run reveals unexpected side effects
  • The plan needs to change mid-execution
  • A verification step fails
  • The user requests changes to the plan at any point
出现以下情况时，停止 skill 并向用户报告：
  • dry-run 显示出意外的副作用
  • 执行过程中需要更改计划
  • 验证步骤失败
  • 用户在任何时候要求修改计划

Example: Database Migration

数据库迁移示例

This is a Tier-2 action because: schema changes are irreversible once applied.

Plan:
  1. Create migration file: ALTER TABLE users ADD COLUMN email_verified BOOLEAN DEFAULT false
  2. Run migration against dev database
  3. Update ORM model to include new column
  4. Add NOT NULL constraint after backfill (separate migration)

Risk: If the backfill is incomplete, the NOT NULL constraint will fail.
      If the migration runs in production prematurely, it could lock the table.

Dry run: psql --dry-run (or migration tool's dry-run flag)
[Wait for user confirmation]
[Execute and verify]
This is a Tier-2 action because: schema changes are irreversible once applied.

Plan:
  1. Create migration file: ALTER TABLE users ADD COLUMN email_verified BOOLEAN DEFAULT false
  2. Run migration against dev database
  3. Update ORM model to include new column
  4. Add NOT NULL constraint after backfill (separate migration)

Risk: If the backfill is incomplete, the NOT NULL constraint will fail.
      If the migration runs in production prematurely, it could lock the table.

Dry run: psql --dry-run (or migration tool's dry-run flag)
[Wait for user confirmation]
[Execute and verify]