菜单
Structured multi-agent software engineering workflow for planning, delegation, review, risk classification, quality gates, and shipping code. Use for software development tasks, implementation planning, code review, debugging, refactoring, and release work.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 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 | agentic-engineering |
| description | Structured multi-agent software engineering workflow for planning, delegation, review, risk classification, quality gates, and shipping code. Use for software development tasks, implementation planning, code review, debugging, refactoring, and release work. |
IMPORTANT - READ THIS FIRST: If
skill_auto_load: trueis set in~/.claude/agentic-engineering.json, this skill is configured to auto-load. Read this entire SKILL.md before taking any action on software development tasks. Do not start implementing until you have read the Rules section below.
The Agentic Engineering system defines how to plan, delegate, review, and ship software using a structured multi-agent workflow. It covers risk classification, adversarial review, task decomposition, and quality gates so that changes are correct, safe, and reviewable. Read the rules files on every session and the reference docs on the triggers described in METHODOLOGY.md §Protocol Details (read on trigger).
Conductor default: act, don't ask. The conductor's job is to complete the goal, not to approve every step. Stop and ask only for destructive/irreversible actions, missing information only the user has, materially ambiguous acceptance criteria, or scope-completion decisions. Repeated stops within one task are a planning signal, not a virtue. See Proactive autonomy in METHODOLOGY.md §Delegation for the full rule, anti-patterns, and stop-frequency thresholds.
METHODOLOGY.md - the assembled kernel: delegation, risk classification, activation preflight, planning gate, task decomposition, and worktree lifecycle; the core rules for when to act directly vs. spawn Workers and Skeptics.
rules/code-standards.md - documentation lookups via Context7, tool discipline (Read always
primary; prefer Glob/Grep when available, Bash rg/grep/find as the sanctioned fallback
otherwise), code quality gates, package management conventions, and browser verification with
agent-browser.
rules/conventions.md - writing style, project structure, session context and memory handling, and git workflow including protected branches and worktree-per-feature conventions.
/ds-help - static, zero-token command reference; lists every slash command with a one-line description./ds-status - read-only resolver dump; shows the resolved mode, profile, and marker with provenance plus a plain-English explainer of what they do and how to change them./ds-brief - interactive planning dialogue; produces the Brief artifact before architect and engineer are spawned. Invoke when operator implies planning intent at session start, or use /ds-brief --from <path> to extract a Brief from an existing PRD./ds-pull-and-install - update an existing agentic-engineering/DinoStack install (or fresh-install if none exists); invoke when the user says "pull and install DinoStack", "update DinoStack", "install the latest DinoStack", "reinstall agentic-engineering", or "update my AE install".Run /ds-help for the full command inventory.
references/skeptic-protocol.md - Skeptic loop orchestration, findings classification (Critical/Major/Minor), sign-off format, adversarial briefs, and the Elevated + Cleanup path.
references/subagent-protocol.md - parallel spawning rules, worktree isolation, check-in behavior, phase breadcrumbs, and task decomposition rules for multi-Worker plans.
references/agent-team.md - named agent roles (engineer, architect, investigator, debugger, security-auditor, orchestration-planner), composed flows, decision rules, and spawn requirements.
references/design-goals.md - design principles and goals of the Agentic Engineering system; read when evaluating whether a proposed change aligns with the system's intent.
references/regression-test-obligation.md - per-finding regression-test obligation: every Skeptic finding fixed during a task must come with a regression test that would have caught it; read when fixing a Skeptic finding to confirm what counts as a valid regression test.
references/doc-sync-obligation.md - per-change doc-sync obligation: a reality-asserting change (alters a count/list/path/convention/behavior an intent-layer doc states) must update the affected docs in the same change; read when a change touches a documented surface.
references/role-models.md - Pi / oh-my-pi per-role model routing and antagonist
reviewer model diversity; read when resolving role-models.yml or spawning reviewers on Pi/omp.
references/model-discovery.md - Pi/oh-my-pi model selection paths (ask-user
wizard, harness-native, pin-by-hand) and the per-role ranking heuristics in
bin/agentic-models; read when seeding role-models.yml.
references/cross-harness-teams.md - agentic-team CLI and team.yml schema for
orchestrating parallel agent teams across multiple AI harnesses; read when using
agentic-team or configuring cross-harness dispatch with team.yml.
references/digest-return-pattern.md - digest-return discipline: when a background loop-running spawn (multi-iteration Skeptic/QA, long investigation) returns, the conductor reads the structured digest and acts - it does not re-read the internal transcript; read when running a multi-unit plan with parallel background loops.
Pi discovers this skill from .pi/skills/agentic-engineering/ for project-local use and from ~/.pi/agent/skills/agentic-engineering/ after global install.
/skill:agentic-engineering when you want the methodology active immediately..pi/prompts/ provide slash-command equivalents for the markdown commands in content/commands/.METHODOLOGY.md at skill load before applying the workflow.commands/<name>.md when a prompt template asks you to run a command.references/ and rules from rules/ on their documented triggers.