Undermybelt
Undermybelt/hermes-skills
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/Undermybelt/hermes-skills --skill subagent-driven-development命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
| name | subagent-driven-development |
| description | Use when executing implementation plans with independent tasks in the current session |
→ Have an implementation plan with independent tasks? → Fresh subagent per task + two-stage review.
Execute plan by dispatching fresh subagent per task, with two-stage review after each: spec compliance review first, then code quality review.
Why subagents: You delegate tasks to specialized agents with isolated context. By precisely crafting their instructions and context, you ensure they stay focused and succeed at their task. They should never inherit your session's context or history — you construct exactly what they need. This also preserves your own context for coordination work.
Core principle: Fresh subagent per task + two-stage review (spec then quality) = high quality, fast iteration
Use when you have a written implementation plan with mostly independent tasks and want to stay in the current session. For cross-session execution, use executing-plans instead.
Before multi-task plans: load long-task-continuation, create checkpoint, include in every implementer prompt.
Before dispatching an implementer, build a SubagentContextPacket instead of
passing full conversation history. Include:
The packet is a compact handoff, not a substitute for evidence. Give raw excerpts or file refs for facts the subagent must verify.
Do not paste full chat transcripts, full session history, or unbounded logs into
SubagentContextPacket. Prefer must-read excerpts, file refs, line/window
hints, and explicit unsafe assumptions.
Use the least powerful model per role: mechanical (1-2 files, complete spec) → fast/cheap. Integration (multi-file, pattern matching) → standard. Architecture/design/review → most capable.
Each implementer prompt must include:
SubagentContextPacket when goal framing, long-task, or multi-agent work is activeTodoCheckpointDraftResumeStateHintThe implementer may update task-local evidence, but the controller owns the consolidated checkpoint.
Implementer subagents report one of four statuses. Handle each appropriately:
DONE: Proceed to spec compliance review.
DONE_WITH_CONCERNS: The implementer completed the work but flagged doubts. Read the concerns before proceeding. If the concerns are about correctness or scope, address them before review. If they're observations (e.g., "this file is getting large"), note them and proceed to review.
NEEDS_CONTEXT: The implementer needs information that wasn't provided. Provide the missing context and re-dispatch.
BLOCKED: The implementer cannot complete the task. Assess the blocker:
Never ignore an escalation or force the same model to retry without changes. If the implementer said it's stuck, something needs to change.
./implementer-prompt.md - Dispatch implementer subagent./spec-reviewer-prompt.md - Dispatch spec compliance reviewer subagent./code-quality-reviewer-prompt.md - Dispatch code quality reviewer subagentNever:
If subagent asks questions:
If reviewer finds issues:
After spec compliance and code quality review pass, update the consolidated checkpoint and run a drift check before moving to the next task.
If subagent fails task:
Required workflow skills:
Subagents should use:
Alternative workflow:
Use when retiring old logic, collapsing duplicate owners, removing fallbacks, or touching schema, persistence, or source-of-truth boundaries while deciding whether to delete old paths, retain compatibility, or stop for confirmation.
Use when defining new features, product behavior, UI/component design, architecture choices, contract changes, or ambiguous medium/high-complexity work before implementation.
Use when the user asks for caveman mode, fewer tokens, brief responses, compressed communication, or otherwise explicitly requests a much shorter answer.
基于 SOC 职业分类