Menú
Read-only view of the skill-candidate backlog. Displays open and dismissed
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
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
| name | ds-skill-candidates |
| description | Read-only view of the skill-candidate backlog. Displays open and dismissed |
| user-invocable | true |
Read-only view of the skill-candidate backlog. Displays open and dismissed candidates detected from recurring workflow friction - each with its domain, count, suggested artifact type, and example note.
No writes, no agent spawns, no network calls. Always exits 0.
/ds-skill-candidates
No subcommands, no flags. Reads .agentic/skill-candidates.md from the
current working directory. If the file is absent: "No skill candidates
detected yet."
Each entry in .agentic/skill-candidates.md has the following structure.
The ## <domain> heading is the unique key. Status is open (written by
the detector on first promotion) or dismissed (set by a human to suppress).
## <domain>
**Count:** <lifetime occurrence count>
**Suggested artifact:** command | named-agent | preset | lint-rule
**First seen:** YYYY-MM-DD
**Last seen:** YYYY-MM-DD
**Status:** open
**Example:** "<one sentence from the triggering session>"
The backlog is written at wrap time (via /ds-wrap Part D LLM extraction and the
hooks/lib/skill-candidate-deep-cluster.js helper) whenever a domain tag
accumulates >= 3 occurrences across sessions. Each entry carries:
## <domain> heading (unique key)command, named-agent, preset, or lint-rule
(routing taxonomy from the detection signal)open (not yet dismissed) or dismissed (operator suppressed)The wrap-time path is the active detection mechanism. A secondary path via
tool_failure_workaround events in .agentic/events.jsonl exists in the
codebase but is dormant - those events are not emitted in ad-hoc sessions.
The command groups entries by **Status:** value:
**Status:** open whose domain is NOT present in
.agentic/.skill-candidates-surfaced. These are the primary action items.**Status:** open whose domain IS
in .agentic/.skill-candidates-surfaced. Conductor has already nudged once.**Status:** dismissed.The command reads .agentic/.skill-candidates-surfaced (one domain per line)
to determine which open entries have already been surfaced at session start.
It never writes to this file.
Skill candidates (.agentic/skill-candidates.md)
OPEN
adapter-interface count: 5 suggested: command
first seen: 2026-05-01 last seen: 2026-05-12
example: "adapter build.sh signatures diverged; had to reconcile manually"
deploy-verification count: 3 suggested: named-agent
first seen: 2026-05-10 last seen: 2026-05-12
example: "ran manual Vercel rollout check; no automated verify step"
OPEN (already surfaced)
worktree-cleanup count: 4 suggested: command
first seen: 2026-05-05 last seen: 2026-05-11
example: "forgot to remove worktree after merge"
DISMISSED
(none)
To create a skill for an open item: create a skill for the domain manually,
or use your usual skill-authoring flow
To dismiss a candidate: edit .agentic/skill-candidates.md and change
**Status:** open to **Status:** dismissed
When .agentic/skill-candidates.md is absent:
No skill candidates detected yet.
The detector runs at the end of each /ds-wrap call and writes candidates here
when a domain tag accumulates >= 3 occurrences. Check back after a few
more sessions, or verify that skill_candidate_detection is true in
.agentic/config.json.
This command is a no-op (displays the absent-file message) when
skill_candidate_detection: false in .agentic/config.json. The file is
the single source of truth; the command never calls the detector itself.
.agentic/skill-candidates.md is committed in consumer projects (via a
!.agentic/skill-candidates.md carve-out in project-scaffolding.yml) so
the backlog travels with the repo and is visible to all team members. It is
NOT committed in the DinoStack methodology source repo itself (the blanket
.agentic/* ignore governs there - intended; DinoStack is the source, not
a consumer).