orchestrate-projects
starsforks
How to install orchestrate-projects?
alfredxw/denova/orchestrate-projects
$npx -y skills add alfredxw/denova --skill orchestrate-projectsUse when the user wants Codex to coordinate a long-running or multi-milestone project, especially when work may span threads, subagents, reviews, local browser/desktop checks, or persistent Goal-mode objectives.
SKILL.md
| 1 | # Orchestrate Projects |
| 2 | |
| 3 | Coordinate long-running work around current evidence, not the first plan. |
| 4 | |
| 5 | ## Workflow |
| 6 | |
| 7 | 1. Start conversationally. Interview the user for goal, constraints, risks, success evidence, and any local-only requirements before turning rough ideas into a plan. |
| 8 | 2. For projects with multiple milestones, create or update `GOALS.md` as the shared roadmap. Organize each milestone by outcome, scope, decisions, blockers, and evidence required. |
| 9 | 3. Keep one active objective at a time. If Goal mode is available, set the current objective from the active milestone and define what evidence is required before marking it complete. |
| 10 | 4. Keep the main thread focused on coordination: objective, constraints, decisions, current state, delegation, and result evaluation. |
| 11 | 5. Delegate bounded implementation, research, testing, or review to subagents or separate threads. Use separate threads when the user may want visible history or later continuation; use subagents for disposable bounded work. |
| 12 | 6. Require workers to return conclusions, changed files, evidence, blockers, and recommended next action. Do not pull full transcripts, large logs, or unrelated details back into the coordinator context. |
| 13 | 7. After each milestone, audit `GOALS.md` against the actual repository state and run a code review when implementation changed. Update the roadmap before activating the next objective. |
| 14 | 8. Use local threads for checks that need the user's machine: signed-in browser state, credentials, desktop apps, permissions, simulators, or device-specific behavior. Feed screenshots, logs, and findings back into the main thread. |
| 15 | 9. When project state changes, report only: |
| 16 | - What's done |
| 17 | - What's next |
| 18 | - Any blockers |
| 19 | 10. For projects with several milestones or parallel workstreams, maintain `progress-dashboard.html` with active goal, milestone status, evidence, blockers, decisions, and recent updates. |
| 20 | |
| 21 | ## Constraints |
| 22 | |
| 23 | - Revise the roadmap when new evidence changes the plan; do not preserve stale assumptions. |
| 24 | - Do not declare a milestone complete until the agreed evidence exists. |
| 25 | - Keep injected context bounded and source-labeled; summarize worker findings instead of copying full histories or logs. |
| 26 | - Ask the user for decisions only when the next step is risky, blocked, or materially changes scope. |
People who liked this also viewed
6 picksType
- lark-workflow-meeting-summary会议纪要整理工作流：汇总指定时间范围内的会议纪要并生成结构化报告。当用户需要整理会议纪要、生成会议周报、回顾一段时间内的会议内容时使用。SkillsJul 2026
- lark-workflow-standup-report日程待办摘要：编排 calendar +agenda 和 task +get-my-tasks，生成指定日期的日程与未完成任务摘要。适用于了解今天/明天/本周的安排。SkillsJul 2026
- lark-approval飞书审批：查询和处理审批待办/已办/实例，搜索可发起审批定义、查看定义详情并发起原生审批实例。当用户要处理审批任务、查看审批实例、搜索或发起审批时使用。审批待办不是飞书任务；非审批类待办走 lark-task。不负责创建审批定义；三方审批定义不走原生提单。SkillsJul 2026
- lark-okr飞书 OKR：管理目标与关键结果。查看和编辑 OKR 周期、目标、关键结果、对齐关系、量化指标和进展记录。当用户需要查看或创建 OKR、管理目标和关键结果、查看对齐关系时使用。不负责：待办任务管理（lark-task）、日程/会议安排（lark-calendar）、绩效评估SkillsJul 2026
- brainstormingYou MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.SkillsJul 2026
- simpleInvoke before any creative or architectural work — feature design, component creation, or behavioral changes. A streamlined brainstorming process optimized for fast, focused decision-making. Gen AgentSkillsMar 2026
