一键导入
workflow-patterns
Patterns for output formats, reflection checkpoints, agent references, and self-evaluation shared across agents and commands.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Patterns for output formats, reflection checkpoints, agent references, and self-evaluation shared across agents and commands.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | Workflow Patterns |
| description | Patterns for output formats, reflection checkpoints, agent references, and self-evaluation shared across agents and commands. |
| version | 2.0.0 |
Use ref attribute to reference agent defined in agents/ directory. readonly attribute indicates whether agent can modify files.
Standard self-evaluation phase for commands and agents that produce reports Brief quality assessment of output Calculate confidence using decision_criteria factors Decision criteria evaluation Confidence score Identify top 1-2 critical issues if confidence below 80 Gap analysis Issue list Append self_feedback section to output Output formatting Self-feedback section Standard self-feedback output section for commands that include self-evaluation XX/100 (based on decision_criteria calculation) - [Critical] Issue description (if any, max 2 total) - [Warning] Issue description (if any)<best_practices> Use output_format for all agents that return structured results Include reflection_checkpoint at key workflow decision points Include prepare_phase for Serena initialization in commands Add self_evaluate_phase for agents producing reports or recommendations Use failure_handling phase in all workflows Use agent_ref syntax for consistent agent references in commands </best_practices>
Output status must use standard criteria (success >= 80, warning 60-79, error less than 60) Reflection checkpoints must include confidence threshold Commands must include prepare_phase for Serena initialization Include failure_handling phase in complex workflows Use self_feedback_output format for self-evaluation results Use agent_ref with readonly attribute for clarity Use standard output_status_criteria thresholds Include confidence score in all structured outputs Define threshold in reflection_checkpoints Include prepare_phase in command workflows Custom status thresholds that differ from standard Omitting failure_handling in complex workflows Omitting Serena initialization in commands<related_skills> Base templates for error escalation, decision criteria, enforcement Parallel execution and timeout configuration Serena MCP operations (memory, symbol search, code navigation) </related_skills>
<related_agents> Verify workflow consistency and checkpoint completeness </related_agents>
This skill should be used when the user asks to "write common lisp", "CLOS", "ASDF", "defpackage", "defsystem", or works with Common Lisp, SBCL, or Coalton. Provides comprehensive Common Lisp ecosystem patterns and best practices.
Context7 MCP documentation retrieval patterns for up-to-date library and API references. Use this skill whenever current library docs, API signatures, version-specific behavior, or migration notes are needed.
Base templates for error escalation, decision criteria, and enforcement. Referenced by agents and commands to avoid duplication.
This skill should be used when working with C++ projects, CMakeLists.txt, Ninja, clang-tidy, clang-format, GoogleTest, Catch2, or Modern C++ (C++20/23/26) language patterns. Provides comprehensive C++ ecosystem patterns and best practices.
This skill should be used when the user works with Effect (Effect-TS) — writing or reviewing Effect.Service definitions, Layer composition (Layer.provide/provideMerge/mergeAll), Effect.scoped resource handling, converting imperative try/catch/async code to the Effect error channel, deriving types from Schema (Schema-as-SSOT), or testing Effect code with @effect/vitest, TestClock, and Layer-based mocks. Provides generalized design principles and minimal reference patterns for Effect 3.x.
This skill should be used when the user asks to "write elisp", "emacs config", "init.el", "use-package", ".el file", "emacs lisp", or "magit". Provides comprehensive Emacs ecosystem patterns and best practices. For org-mode, use org-ecosystem skill.