القائمة
Static, zero-token command reference for the agentic-engineering skill.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | ds-help |
| description | Static, zero-token command reference for the agentic-engineering skill. |
| user-invocable | true |
Static, zero-token command reference for the agentic-engineering skill. Prints every slash command with a one-line description, grouped by intent, plus usage patterns for inspecting, deliberately invoking, and tuning the skill. Writes nothing. Always exits 0.
Implementation: bin/agentic-help (Python 3 stdlib).
agentic-help
No subcommands, no flags. The help text is a compile-time constant; the command reads no files and depends on no environment state.
A fixed reference block: the command inventory grouped under "Inspect &
configure", "Plan & build" (includes /ds-brief, /ds-implement-ticket,
/ds-ticket-triage, /ds-init-project, /ds-skeptic), "Maintain & curate", and
"Audit & improve the methodology", followed by a "Usage patterns" section
covering how to inspect current config, deliberately invoke the skill when
it is disabled or in opt-in mode, change the workflow strictness, and turn
the skill off.
0 - always. The command is static and read-only; it has no inputs to
validate and never raises.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