terse
/terse
WellForge terse mode — the token-efficient conversational output cue, orthogonal to rigor tier. Use whenever running $wf-spike (terse by default), when $wf-orchestrate or $wf-implement is given --terse/--no-terse, when the main-loop $wf-terse toggle is invoked, or when deciding whether a piece of output should be compressed. Authoritative reference for the terse cue directive text, the byte-identical invariant, which artifacts are exempt, the activation matrix, and $wf-terse session semantics.
- Author
- matteocodogno ↗
- Repository
- wellforge ↗
- Licence
- MIT
- Last repository change
- 13.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 13.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
WellForge terse mode — the token-efficient conversational output cue, orthogonal to rigor tier. Use whenever running $wf-spike (terse by default), when $wf-orchestrate or $wf-implement is given --terse/--no-terse, when the main-loop $wf-terse toggle is invoked, or when deciding whether a piece of output should be compressed. Authoritative reference for the terse cue directive text, the byte-identical invariant, which artifacts are exempt, the activation matrix, and $wf-terse session semantics.
Original author description
WellForge terse mode — the token-efficient conversational output cue, orthogonal to rigor tier. Use whenever running $wf-spike (terse by default), when $wf-orchestrate or $wf-implement is given --terse/--no-terse, when the main-loop $wf-terse toggle is invoked, or when deciding whether a piece of output should be compressed. Authoritative reference for the terse cue directive text, the byte-identical invariant, which artifacts are exempt, the activation matrix, and $wf-terse session semantics.
How it works
- Terse cue
- Byte-identical invariant
- Artifact exemption
- Activation matrix
- $wf-terse semantics
SKILL.md preview
--- name: terse description: > WellForge terse mode — the token-efficient conversational output cue, orthogonal to rigor tier. Use whenever running $wf-spike (terse by default), when $wf-orchestrate or $wf-implement is given --terse/--no-terse, when the main-loop $wf-terse toggle is invoked, or when deciding whether a piece of output should be compressed. Authoritative reference for the terse cue directive text, the byte-identical invariant, which artifacts are exempt, the activation matrix, and $wf-terse session semantics. --- # Terse mode — token-efficient conversational output Conversational output, orchestration/handoff narration, and status recaps are pure overhead: they cost output tokens without adding substance. **Terse mode** is a plain-text directive, modelled one-to-one on the existing effort cue (`skills/rigor-tiers/SKILL.md`), that dispatching commands prepend to each agent's task prompt — or that the spike main loop self-applies. It is **orthogonal to rigor tier**: any tier may run terse, and terse never changes which gates, agents, or approvals run. ## Terse cue The injected directive (verbatim — do not paraphrase when prepending it to a task prompt): ``` TERSE MODE — output tokens are the cost. Drop filler, preamble, and restating the question. Prefer fragments over sentences. Substance only. INVARIANT: never alter code blocks, shell commands, file paths, identifiers, or error messages — reproduce them byte-for-byte. EXEMPT: when writing spec.md / plan.md / tasks.md / design.md / an ADR / eval*.md, ignore terse mode entirely and follow the full format contract. ``` Prepend this cue next to the effort cue (if the rigor-tiers skill is also in play) whenever terse is resolved on. For the spike main loop, the loop applies the cue to itself — there is no subagent task prompt to prepend to. ## Byte-identical invariant **Terseness MUST NOT alter code blocks, shell commands, file paths, identifiers, or error messages.** These are reproduced byte-for-byte identical to their non-terse form. This is a **correctness and safety invariant, not a style preference**. Terse compression targets prose — filler, preamble, restated context, narration — never the literal payload a human or a downstream tool will copy, paste, or execute. A terse transform that silently edited a shell command or a file path would not just read worse, it would cause real damage (wrong command run, wrong file touched, a masked error message). Treat any drift between a terse rendering and the canonical content of a code span, command, path, identifier, or error message as a bug to fix, not a tradeoff to accept. ## Artifact exemption Terse mode **NEVER applies** when writing any of the spec-driven or governance artifacts: - `spec.md` - `plan.md` - `tasks.md` - `design.md` - an ADR - `eval.md` / `eval-report.md` These artifacts follow their **full format contract** regardless of whether terse mode is active for the surrounding conversation. The commands that write them (`spec`, `plan`, `design`, `tasks`, `wf-adr-writer`, `eval`) load the spec-driven skill's format mandate, which takes precedence — terse is a conversational-output cue, not a document-generation mode, and must not leak into a contracted artifact. This is backstopped by the existing drift/format checks and by the evaluator, which would surface any fidelity regression in these files as a score drop. ## Activation matrix Terse is resolved as a boolean per run/session, independent of rigor tier: | Surface | Activation | Notes | |---|---|---| | `$wf-spike` | **ON by default** | main loop self-applies the cue; `--no-terse` opts out | | `$wf-orchestrate` | `--terse` flag (**OFF by default**) | parsed/stripped in Step 0 — Resolve, alongside `--mode`; prepended per dispatched agent | | `$wf-implement` | `--terse` flag (**OFF by default**) | same Step 0 handling as orchestrate | | main loop | **`$wf-terse` toggle** command | session-level directive, independent of any command flag | | `mvp` / `production` (no flag) | **OFF** | terse is never implied by tier alone outside spike | `--terse` / `--no-terse` is a separate axis from `--mode`/rigor tier — any tier can be run terse; spike merely defaults it on. A `--no-terse` flag on `$wf-spike` restores normal verbosity for that run. ## $wf-terse semantics `$wf-terse` is a main-loop session toggle, not a one-shot flag — it has no arguments and flips state on each invocation: ``` $wf-terse → "Terse mode: ON until you run $wf-terse again." $wf-terse (again) → "Terse mode: OFF." ``` Because the plugin has no persistent main-loop state store, "session state" is realized the WellForge way: as a stated directive the command emits, which governs subsequent conversational output for the rest of the session (or until toggled off again) — the same pattern the effort cue uses, just re-triggerable. The artifact exemption above still applies in full while the toggle is ON: writing a spec-driven artifact mid-session ignores the active terse state.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · matteocodogno/wellforge | 100 | MIT |
| adityavora16/terse | 100 | MIT |
| mrlemoos/galicia | 100 | MIT |
| matteocodogno/wellforge | 100 | MIT |
Database snapshot: 13.11.2026 · package version 48975bf8ee3a (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100using-terse-brain
Build and maintain a durable personal knowledge base ("brain") in a TERSE store. Use when the user asks about `terse-brain`, research wiki, llm-wiki, source-cited notes, or long-lived knowledge that compounds across sessions — not a scratchpad and not the generic `default` TERSE namespace. - 100terse-output
Cut the tokens the agent WRITES, not just what it reads. Activate when the user asks for terse/concise/brief output, says responses are too long, wants to save output tokens or cost, or runs /justokenmax:terse — then answer in a compressed style that preserves all technical… - 100rigor-tiers
WellForge rigor tiers — match ceremony to stakes. The spike / mvp / production vocabulary that governs how much of the pipeline runs (agents, approval gates, models, quality gates, eval) for a feature. Use whenever running /wellforge:spike, when /wellforge:orchestrate or… - 90terse-output
Opt-in reply style with shorter prose in your own replies; code, commands, paths, errors, numbers and quotes stay exact. USE WHEN named. NOT FOR shrinking inputs or written docs. - 90using-terse
Read, write, and query durable structured state in a TERSE store. Use whenever the user asks about TERSE, or when the session needs shared persistent memory / notes / project state that must survive across turns, sessions, or agents — not a scratchpad and not a general database. - 100token-efficient
Use when the user activates compressed output mode ("caveman mode", "terse", "compress") — drops conversational filler while preserving artifact quality. Deactivates on "normal mode" or "verbose". ADR-003 scopes this to conversation only.