dev-architecture-playbook
仓库创建 2025年12月9日最近提交 9 天前SkillHot 收录 20 天前
▸ 精选理由
适合在开始大规模开发前统一流程与明确责任,能防止过早实现细节。
这个 Skill 做什么
在产品意图到实施全生命周期中路由并组合合适的技能链,定义关卡与交付顺序。
把产品意图一路路由到设计、实现、测试、发布和运维,按交付顺序组合合适的技能链并定义关卡与交付标准。当你要把一个想法或仓库变成生产级计划,或需要一个完整的架构与执行路径时用得上,能避免提前编码导致的返工。特别之处在于它会选择最小可用技能组合并在每个阶段设定门禁,保证契约先行再开发。
▸ 展开 SKILL.md 英文原文
Route full software-development architecture work from product intent through design, implementation, testing, release, and operations. Use when the user asks for a complete development architecture, wants to know which Spellbook skills to combine, needs an execution path across PRD/spec/API/data/security/performance/release/SRE, or asks to turn an idea or repo into a production-ready engineering plan.
239
Stars
23
Forks
40
仓库内 Skill
+7
7 日增星
安装 / 使用
给你的 Agent 一句话(通用)
帮我安装这个 skill:https://raw.githubusercontent.com/majiayu000/spellbook/main/skills/dev-architecture-playbook/SKILL.md或 curl 直取 SKILL.md
curl -fsSL "https://raw.githubusercontent.com/majiayu000/spellbook/main/skills/dev-architecture-playbook/SKILL.md"SKILL.MD 节选查看完整文件 ↗
# Dev Architecture Playbook ## Purpose Use this as the lifecycle router before starting broad product or architecture work. It chooses the minimum useful skill chain, defines gates, and prevents starting implementation before the required contracts exist. ## Route Classify the request first: | Request | Primary Skills | Output | |---|---|---| | Idea, product direction, or market/user problem | `product-discovery`, `prd-master` | Product brief, user stories, success metrics | | Architecture or module boundaries | `architecture-foundation`, `technical-spec`, `elegant-architecture` | Architecture spec, boundaries, rejected alternatives | | API, auth, data, or schema contract | `api-design`
via SKILL·HOT · 数据来自 GitHub 公开信息 · 原文版权归作者所有