dev-pipeline

仓库创建 2026年7月6日最近提交 21 天前SkillHot 收录 20 天前
▸ 精选理由

支持动态后台 Workflow 或会话内委派,适合分叉与可重复任务。

这个 Skill 做什么

提供 Explore→Plan→Implement→Review 的分层开发流水线与运行模式。

把开发流程拆成四步可复用的节奏:Explore → Plan → Implement → Review,可以在会话里逐步推进,也能以后台 Workflow 自动化运行。适合需要把一个功能或修复按阶段推进、多人协作或希望把讨论和执行分离时用。特点是有明确分层和运行模式,能先把问题刨根问底再开始实现,支持选择性自动化和把输出隔离到后台。

▸ 展开 SKILL.md 英文原文

Tiered plan→explore→implement→review pipeline (Haiku explores, Opus plans, Sonnet implements, Opus reviews). On invocation, optionally grills the user first for a sharp understanding, then asks whether to run as a dynamic background Workflow or as inline in-session delegation. Use when the user wants to build/implement a feature or fix through the tiered pipeline. Pass the task as args.

自动化集成构建流水线探索计划实现工作流通用
0
Stars
0
Forks
1
仓库内 Skill
+0
7 日增星
安装 / 使用
给你的 Agent 一句话(通用)
帮我安装这个 skill:https://raw.githubusercontent.com/shaneomac1337/dotclaude/master/skills/dev-pipeline/SKILL.md
或 curl 直取 SKILL.md
curl -fsSL "https://raw.githubusercontent.com/shaneomac1337/dotclaude/master/skills/dev-pipeline/SKILL.md"
SKILL.MD 节选查看完整文件 ↗
# dev-pipeline

A tiered build pipeline — **Explore → Plan → Implement → Review** — that can run two ways:

- **Dynamic** — a background `Workflow` script (`pipeline.js`). Deterministic control flow, headless agents, output kept out of the main context. Best for larger fan-out, repeatable runs, and keeping the conversation clean.
- **Inline** — the same four tiers, but delegated *in this session* via the `Agent` tool. You stay in the loop, see each step, and can steer between tiers. Best for smaller tasks and when the user wants visibility/control.

Both use the same model tiering: **Haiku** explores (cheap, parallel, read-only), **Opus** plans, **Sonnet** implements, **Opus** reviews (judge
via SKILL·HOT · 数据来自 GitHub 公开信息 · 原文版权归作者所有