Framework Orchestrator by daffy0208/ai-dev-standards
npx skills add https://github.com/daffy0208/ai-dev-standards --skill 'Framework Orchestrator'Framework Orchestrator 是一个元技能,用于在整个项目生命周期中协调所有其他技能和框架。它会分析您的项目,识别适当的模式,并以最优顺序编排框架和技能的执行。
可以将其视为: 您的 AI 项目经理,知道何时应用何种方法论。
在以下情况下使用 Framework Orchestrator:
分析项目并将其归类为以下三种模式之一:
特征:
示例:
时间线: 1-5 天
特征:
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
示例:
时间线: 4-12 周
特征:
示例:
时间线: 8-20 周
根据模式,推荐框架执行顺序:
协调技能:
阶段 1:探索与验证
阶段 2:架构与设计
阶段 3:开发
阶段 4:测试与验证
阶段 5:部署与发布
包含模式 B 的所有阶段,并且:
阶段 2b:AI 架构(与标准架构并行)
阶段 3b:AI 开发(与标准开发集成)
阶段 4b:AI 测试(额外的测试层)
执行各阶段并设置验证关口:
进入阶段 2 (设计):
进入阶段 3 (开发):
进入阶段 4 (测试):
进入阶段 5 (部署):
根据当前阶段编排技能:
探索阶段技能:
设计阶段技能:
开发阶段技能:
测试阶段技能:
部署阶段技能:
发布后技能:
项目分析:
推荐顺序:
第 1 周:探索
第 2 周:架构 5. bmad-method 技能 → 业务模型 + 架构对齐 6. design_prototyping_framework → 线框图 7. ux-designer 技能 → 用户旅程 8. api-designer 技能 → API 设计 9. security-architect 技能 → 威胁模型
第 3-6 周:开发 10. full_stack_dev_framework 11. frontend-builder 技能 → 构建 React UI 12. api-designer 技能 → 构建后端 13. quality-assurance 技能 → 持续测试
第 7 周:测试 14. testing_validation_framework 15. quality-assurance 技能 → 测试金字塔 16. usability-tester 技能 → 用户测试 17. security-architect 技能 → 安全测试
第 8 周:部署 18. deployment_devops_framework 19. deployment-advisor 技能 → 部署到生产环境 20. go-to-market-planner 技能 → 发布计划
项目分析:
推荐顺序:
第 1-2 周:探索 (与模式 B 相同)
第 3-4 周:架构
第 5-9 周:开发
第 10-11 周:测试
第 12 周:部署
项目分析:
推荐顺序:
第 1 天:
第 2 天: 3. 构建后端 + 前端 4. quality-assurance 技能 → 单元测试
第 3 天: 5. testing-strategist 技能 → 集成测试 6. deployment-advisor 技能 → 部署到预发布环境,然后生产环境
不要直接跳到框架。首先理解:
不要跳过验证检查点。每个关口确保:
某些工作可以并行运行:
如果项目演进:
不要一次性激活所有技能。按顺序编排:
反模式: 将模式 B (新产品) 当作模式 A (简单功能) 处理 结果: 跳过探索,构建错误的东西
修复: 如果存在任何不确定性,默认使用模式 B
反模式: 没有设计就直接进入开发 结果: 返工、遗漏需求、安全漏洞
修复: 遵守顺序,验证阶段关口
反模式: 为一个按钮颜色更改使用完整的模式 B 编排 结果: 在不必要的过程上浪费时间
修复: 对于真正简单的工作,模式 A 是有效的
反模式: 在没有适当架构阶段的情况下构建 AI 系统 结果: 技术债务、性能差、重写
修复: 模式 C 需要全面的编排
反模式: 在架构不完整的情况下进入开发 结果: 在不稳固的基础上构建,开发中途受阻
修复: 强制执行阶段关口,记录准备情况
使用 Framework Orchestrator 时,产生:
模式识别
编排计划
当前阶段状态
风险与适应计划
成功的编排意味着:
请记住: 编排器确保您在正确的时间应用正确的方法论。这是有序开发与混乱挣扎之间的区别。
每周安装量
0
代码仓库
GitHub 星标数
18
首次出现
1970年1月1日
安全审计
The Framework Orchestrator is the meta-skill that coordinates all other skills and frameworks throughout your project lifecycle. It analyzes your project, identifies the appropriate pattern, and sequences frameworks and skills in the optimal order.
Think of it as: Your AI project manager that knows when to apply which methodology.
Use Framework Orchestrator when:
Analyze the project and categorize into one of three patterns:
Characteristics:
Examples:
Timeline: 1-5 days
Characteristics:
Examples:
Timeline: 4-12 weeks
Characteristics:
Examples:
Timeline: 8-20 weeks
Based on pattern, recommend framework sequence:
Coordinating Skills:
Phase 1: Discovery & Validation
Phase 2: Architecture & Design
Phase 3: Development
Phase 4: Testing & Validation
Phase 5: Deployment & Launch
All Pattern B phases, PLUS:
Phase 2b: AI Architecture (parallel with standard architecture)
Phase 3b: AI Development (integrated with standard development)
Phase 4b: AI Testing (additional testing layer)
Execute phases with validation gates:
Entry to Phase 2 (Design):
Entry to Phase 3 (Development):
Entry to Phase 4 (Testing):
Entry to Phase 5 (Deployment):
Orchestrate skills based on current phase:
Discovery Phase Skills:
Design Phase Skills:
Development Phase Skills:
Testing Phase Skills:
Deployment Phase Skills:
Post-Launch Skills:
Project Analysis:
Recommended Sequence:
Week 1: Discovery
Week 2: Architecture 5. bmad-method skill → Business model + architecture alignment 6. design_prototyping_framework → Wireframes 7. ux-designer skill → User journeys 8. api-designer skill → API design 9. security-architect skill → Threat model
Week 3-6: Development 10. full_stack_dev_framework 11. frontend-builder skill → Build React UI 12. api-designer skill → Build backend 13. quality-assurance skill → Continuous testing
Week 7: Testing 14. testing_validation_framework 15. quality-assurance skill → Test pyramid 16. usability-tester skill → User testing 17. security-architect skill → Security testing
Week 8: Deployment 18. deployment_devops_framework 19. deployment-advisor skill → Deploy to production 20. go-to-market-planner skill → Launch plan
Project Analysis:
Recommended Sequence:
Week 1-2: Discovery (same as Pattern B)
Week 3-4: Architecture
Week 5-9: Development
Week 10-11: Testing
Week 12: Deployment
Project Analysis:
Recommended Sequence:
Day 1:
Day 2: 3. Build backend + frontend 4. quality-assurance skill → Unit tests
Day 3: 5. testing-strategist skill → Integration tests 6. deployment-advisor skill → Deploy to staging, then production
Don't jump to frameworks. First understand:
Don't skip validation checkpoints. Each gate ensures:
Some work can run in parallel:
If project evolves:
Don't activate all skills at once. Sequence them:
Antipattern: Treating Pattern B (new product) as Pattern A (simple feature) Result: Skip discovery, build wrong thing
Fix: If any uncertainty exists, default to Pattern B
Antipattern: Jump straight to development without design Result: Rework, missed requirements, security gaps
Fix: Respect the sequence, validate phase gates
Antipattern: Use full Pattern B orchestration for a button color change Result: Waste time on unnecessary process
Fix: Pattern A is valid for truly simple work
Antipattern: Build AI system without proper architecture phase Result: Technical debt, poor performance, rewrites
Fix: Pattern C requires comprehensive orchestration
Antipattern: Move to development with incomplete architecture Result: Build on shaky foundation, blockers mid-development
Fix: Enforce phase gates, document readiness
When using Framework Orchestrator, produce:
Pattern Identification
Orchestration Plan
Current Phase Status
Risk & Adaptation Plan
Successful orchestration means:
Remember: The orchestrator ensures you apply the right methodology at the right time. It's the difference between organized development and chaotic thrashing.
Weekly Installs
0
Repository
GitHub Stars
18
First Seen
Jan 1, 1970
Security Audits
开源项目教练指南 - 诊断问题、制定行动计划、优化开源项目运营
31,600 周安装