> ## Documentation Index
> Fetch the complete documentation index at: https://docs.comet.rpamis.com/llms.txt
> Use this file to discover all available pages before exploring further.

# tweak preset

> tweak is the OpenSpec-backed lightweight preset: open -> build -> verify -> archive, skipping brainstorming and full planning while treating delta spec as a first-class artifact.

`tweak` is Comet's lightweight OpenSpec path. It runs `open -> build -> verify -> archive`, skips brainstorming and full planning, but treats **delta spec as a first-class artifact** and builds through OpenSpec apply.

<p align="center">
  <img src="https://mintcdn.com/comet-bb5f5294/vM44yjOkcpkEH_kN/assets/tweak-preset-illustrations/01-tweak-tuning-board.png?fit=max&auto=format&n=vM44yjOkcpkEH_kN&q=85&s=3721b374426aa3fda5bc03514a6ff29e" alt="Xiaoyu uses a delta spec sheet to make a single-point tweak, then connects apply, full verify, and the upgrade signal when scope grows" width="800" data-path="assets/tweak-preset-illustrations/01-tweak-tuning-board.png" />
</p>

<p align="center">
  tweak is not a casual edit path; it uses delta spec and OpenSpec apply for bounded medium changes.
</p>

Use tweak for configuration changes, documentation or prompt improvements, behavior tuning, and brownfield changes that need a delta spec but do not require full deep design.

<Tip>
  Normally you only need <code>/comet</code>. When project configuration selects Classic, the
  internal <code>/comet-classic</code> router recognizes a request that fits one OpenSpec change
  without full design and prefers tweak automatically.
</Tip>

## When to use it

Use tweak when all of these are true:

* The work fits one OpenSpec change.
* You do not need a Superpowers Design Doc or full implementation plan.
* There is no cross-module architectural coordination.
* Scope is predictable.

If you are unsure, start with tweak. Upgrade signals pause and let you move to full.

## Relationship to full and hotfix

| Dimension        | tweak                              | full                                            | hotfix                             |
| ---------------- | ---------------------------------- | ----------------------------------------------- | ---------------------------------- |
| Goal             | Adjust behavior or content         | New capability, architecture, large requirement | Fix a bug                          |
| Flow             | open -> build -> verify -> archive | open -> design -> build -> verify -> archive    | open -> build -> verify -> archive |
| Build style      | OpenSpec apply                     | Superpowers plan + execution choice             | Direct task loop                   |
| Delta spec       | First-class artifact               | Normal via PRD/spec design                      | Exception only                     |
| Root-cause check | No                                 | No                                              | Yes                                |
| Commit prefix    | `tweak:`                           | Normal project convention                       | `fix:`                             |

## Flow

```mermaid theme={null}
flowchart TD
    Start["Change description"] --> S1["Fast open"]
    S1 --> Delta{"Affects existing spec?"}
    Delta -->|yes| D["Create delta spec"]
    Delta -->|no| S2["OpenSpec apply build"]
    D --> S2
    S2 --> Esc{"Upgrade signal?"}
    Esc -->|yes| Stop["Pause: continue tweak or upgrade full"]
    Esc -->|no| Guard["Build guard"]
    Stop -->|continue| Guard
    Stop -->|upgrade| Up["preset-escalate -> design"]
    Guard --> V["Verify"]
    V --> HasDelta{"Has delta spec?"}
    HasDelta -->|yes| Full["force full verify"]
    HasDelta -->|no| Light["light verify"]
    Full --> Done{"Pass?"}
    Light --> Done
    Done -->|yes| Archive["Archive after confirmation"]
    Done -->|no| Fix["Verification failure decision"]
```

## OpenSpec apply build

The apply path belongs to tweak. The agent must read `openspec instructions apply --change <name> --json`, consume listed context files, complete tasks, run relevant tests, and commit focused changes. Full workflow must not reuse this path.

`init <name> tweak` writes the same lightweight execution defaults as hotfix (`build_mode: direct`, `tdd_mode: direct`, `review_mode: off`, `verify_mode: light`) but leaves `isolation` as `null`. At entry, tweak asks you to explicitly keep the current branch, create a branch, or create a worktree. The confirmed `isolation` and `bound_branch` describe the real execution workspace, and later accidental branch switches are blocked. `tdd_mode: direct` skips Red-Green-Refactor but still requires relevant tests and regression evidence.

## Verification

If a tweak has a delta spec, verification is forced to full so OpenSpec consistency is checked. Without a delta spec, light verification is usually enough.

## Upgrade signals

Tweak pauses for qualitative signals such as cross-module coordination, need to split into multiple OpenSpec changes, schema change, public API change, or deep architecture issue. File count is a tripwire for user choice, not an automatic upgrade.

Upgrade through:

```bash theme={null}
node "$COMET_STATE" transition <name> preset-escalate
```

## Recovery

Tweak is idempotent. After interruption, run `/comet`. When configuration selects Classic, the internal `/comet-classic` router reads `.comet.yaml` and returns to `/comet-tweak` when needed.

## Next steps

* [hotfix preset](/en/presets/hotfix)
* [Auto-transition](/en/concepts/auto-transition)
* [Decision points](/en/concepts/decision-points)
* [Verify phase](/en/phases/verify)