Menü
Interactive command to view and change agentic-engineering settings in-session.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
| name | ds-config |
| description | Interactive command to view and change agentic-engineering settings in-session. |
| user-invocable | true |
Interactive command to view and change agentic-engineering settings in-session. Reads the current resolved state, prompts for which setting to change and the new value, writes the correct file, and confirms what changed and when it takes effect.
Implementation: bin/agentic-config (Python 3 stdlib; reuses resolver logic
from bin/agentic-status).
/ds-config
No subcommands or flags. Selection is done interactively.
Resolve and display current settings. Reads ~/.claude/agentic-engineering.json
(mode, profile), the project AGENTS.md markers, and .agentic/config.json (toggles).
Displays each setting with its current value and source (global / project / marker).
Reuses the same resolver as /ds-status so the two commands never diverge.
Setting selection prompt. Grouped:
~/.claude/agentic-engineering.json
or AGENTS.md marker, depending on scope prompt..agentic/config.json: auto_merge_on_ci_green,
commit_telemetry, capability_preflight_mode, abdication_guard_enabled,
ticket_driven, and any additional config-file toggles.Value selection prompt. Lists valid values for the chosen setting, with the
current default marked. For boolean toggles: true / false. For enumerated
settings: the full set (e.g. off / offer / require for ticket_driven).
Scope prompt (mode and profile only). When the chosen setting can live in
more than one place, prompt: apply globally (~/.claude/agentic-engineering.json)
or to this project only (AGENTS.md marker / .agentic/config.json). Default =
project when running inside a git repo.
Write the file. Atomic write (tmp + rename) for JSON files. For AGENTS.md
markers, appends or updates the relevant agentic-engineering-profile: line.
Honors the preset-over-profile precedence rule when writing profile changes.
Confirm and state effect timing.
.agentic/config.json) take effect at the next session
start.export <VAR>=1 line for the operator to use.Loop or exit. After each change, offer to change another setting or exit.
File-settable (full support):
| Setting | Key | File |
|---|---|---|
| Mode | mode | ~/.claude/agentic-engineering.json |
| Profile | profile | ~/.claude/agentic-engineering.json or AGENTS.md |
| Auto-merge on CI | auto_merge_on_ci_green | .agentic/config.json |
| Commit telemetry | commit_telemetry | .agentic/config.json |
| Capability preflight | capability_preflight_mode | .agentic/config.json |
| Abdication guard | abdication_guard_enabled | .agentic/config.json |
| Ticket-driven | ticket_driven | .agentic/config.json |
Env kill-switches (print-only, not applied to running session):
AE_SINGULARITY_GUARD_DISABLE, AE_TIER_GUARD_DISABLE, AGENTIC_QUIET.
When an equivalent config toggle exists (e.g. abdication_guard_enabled
covers AE_ABDICATION_GUARD_DISABLE), offer to set that instead.
Out of scope: identity (owned by /ds-identity), team.yml
(v1 deferral), AGENTS.md source-of-truth conflicts across multiple nested files.
mode opt-in footgun handlingSetting mode to opt-in in ~/.claude/agentic-engineering.json is the one
setting that silently disables the methodology on every project that lacks an
agentic-engineering: opt-in marker in its AGENTS.md - which is most projects.
This is the opposite of the intent when a user just wants "tighter control".
Pre-write gate (LLM layer). Before invoking bin/agentic-config mode opt-in,
warn the user that:
opt-in mode makes the methodology inactive by default in all repos.agentic-engineering: opt-in in its AGENTS.md will
silently stop using the methodology after this change./ds-disable) rather than switching the global
default.Confirm that the user wants to proceed. Only invoke the binary after confirmation. Do not run the binary speculatively - the binary writes the file immediately on invocation and prints its warning only after the write is committed.
If the user confirms, invoke bin/agentic-config mode opt-in. The binary also
prints a post-write reminder listing the affected repos (any repo without an
opt-in marker), but the LLM-layer gate is the primary safety check.
Settings that write to ~/.claude/agentic-engineering.json or .agentic/config.json
take effect at the next session start. The command confirms this explicitly
after each write. No restart is required for env kill-switch exports (those apply
to the current shell session when set before launching Claude).
0 - change applied successfully or operator chose to exit without changes1 - I/O error (read-only file, permission denied, malformed JSON)2 - operator aborted at confirmation prompt (no files modified)Apply when the user mentions any software development work: implementing features, fixing bugs, reviewing or refactoring code, debugging, testing, deploying, working with agents or subagents, making architecture decisions, setting up projects, managing dependencies, writing scripts, or any task that involves reading, writing, or reasoning about code and systems.
Agentic Engineering Protocol for Hermes - structured delegation model, risk classification, adversarial review loops, code quality gates, git workflow conventions, and named agent definitions. Load this skill when doing AI-assisted software development with Hermes Agent.
Apply when the user mentions any software development work: implementing features, fixing bugs, reviewing or refactoring code, debugging, testing, deploying, working with agents or subagents, making architecture decisions, setting up projects, managing dependencies, writing scripts, or any task that involves reading, writing, or reasoning about code and systems.
Pre-implementation technical design agent. Spawn when you need a structured technical plan before writing code. Reads the codebase, identifies patterns and constraints, evaluates approaches, and produces a concrete plan a Worker can execute directly. Never writes or modifies files.
General-purpose implementation agent. Spawn for any code change: new features, bug fixes, refactors, configuration changes, or script writing. Reads the codebase to understand conventions, implements the change, runs quality gates, and returns a clear summary of what was done. This is the standard Worker for all Elevated-risk implementation tasks.
Cheap per-turn stop-condition check for open-goal loops. Spawned by the conductor ONLY after an Elevated iteration produces a clean Skeptic sign-off, to evaluate the operator-declared goal_condition and return continue-vs-stop only - never for a Low/Trivial iteration (no Skeptic sign-off exists to run after; the conductor evaluates goal_condition directly there instead). Tier 1 (haiku) leaf agent - read-only, no subagent spawning, never runs in place of, before, or concurrently with a Skeptic review. Does NOT review correctness or safety and does NOT raise, waive, or comment on Skeptic findings. Returns BLOCKED only as a structural guard when spawned without a confirmed Skeptic sign-off; the conductor handles this BLOCKED as a fallback to direct evaluation, NOT as the generic Worker-BLOCKED-means-cap_reached-escalation semantics in content/references/subagent-protocol.md - a BLOCKED return here never halts the loop. On any other failure (unavailable, errored, timeout, malformed output) the conductor falls bac