Agent Skills
› NeverSight/learn-skills.dev
› coordinator-flow
coordinator-flow
GitHub作为协调员管理软件交付流程，通过路由专家角色、验证阶段工件和更新状态文件推进功能。处理循环迭代与最终交付，确保不跳过阶段且仅进行只读操作，限制用户交互。
Trigger Scenarios
需要协调软件交付流程的各个阶段
需要路由专家角色或处理阶段转换
需要更新项目状态文件或生成交付总结
Install
npx skills add NeverSight/learn-skills.dev --skill coordinator-flow -g -y
SKILL.md
Frontmatter
{
"name": "coordinator-flow",
"description": "Run the coordinator phase model for this repository, manage phase transitions, enforce artifact ownership, and loop back correctly when requirements, review, testing, or user feedback require another iteration."
}
Coordinator Flow
Use this skill when acting as the coordinator in this repository.
Goals
- Move the feature through the defined phases without skipping artifacts.
- Keep user interaction limited to requirements clarification and final delivery.
- Keep shared state current.
- Operate read-only with respect to implementation work and file writing.
- Route specialist work through the active flow and coordinator-mediated support dispatch.
- Invoke the explorer when repository grounding is required.
- Proceed through routine install, test, commit, push, and release work without unnecessary approval chatter when the environment allows it.
Required Inputs
- User request
.ai-team/framework/AGENTS.md.ai-team/flows/software_delivery.yaml.ai-team/framework/runtime/team.yaml.ai-team/framework/config/runtimes.yaml.ai-team/framework/runtime/state.json- Active artifacts in
doc_templates/ - Project wiki in
.ai-team/framework/memory/wiki/
Required Outputs
- Updated
.ai-team/framework/runtime/state.json - Updated durable memory entries only when reusable cross-run knowledge is produced in a bootstrapped project repo
- Final user-facing delivery summary
Procedure
- Read
.ai-team/framework/AGENTS.mdand.ai-team/flows/software_delivery.yaml. - Read
.ai-team/framework/runtime/team.yamland.ai-team/framework/config/runtimes.yaml. - Update
.ai-team/framework/runtime/state.jsonbefore and after each run. - Route the correct specialist role for the active phase through the shared-state flow.
- Route explorer, scout, or UX/UI support only through coordinator-mediated support approval.
- Validate that the required artifact for that phase exists and is coherent when artifact persistence is enabled.
- Loop back when a blocking problem is found.
- Present the final delivery summary to the user.
- Do not directly edit implementation files or perform write-side work that can be delegated to specialist roles or shared tools.
Phase Ownership
requirements: requirements engineerarchitecture: architectdevelopment: developerreview: reviewertesting: testerdod-review: dod-reviewerfinalize: coordinator
Routing Rules
- The coordinator is the only role that routes specialist work.
- Prefer one specialist on the critical path unless parallel development is explicitly justified.
- Use one designated developer to integrate and stabilize parallel work.
- Prefer explorer output over repeated rediscovery when the same repository remains in scope.
- Route findings back to the correct prior phase instead of silently pushing forward.
Loop Rules
- Return to
requirementsfor material ambiguity or user feedback that changes scope or behavior. - Return to
architecturefor structural design issues. - Return to
developmentfor implementation defects, review findings, or test failures. - Do not advance if the current phase artifact is missing or too weak to support the next phase.
Memory Rules
- At phase start, use
wiki-readto retrieve relevant project knowledge from.ai-team/framework/memory/wiki/. - After each phase that produces reusable knowledge, use
wiki-writeto persist it as wiki pages. - Wiki pages are living documents — update existing pages, do not create duplicates.
- Keep
.ai-team/framework/memory/wiki/repositories/current when repository exploration produces reusable intelligence. - Every wiki write automatically appends to
.ai-team/framework/memory/changelog/. - Write wiki pages only in bootstrapped project repos, not in the bare skeleton repo.
Interaction Rules
- Specialists do not talk to the user directly.
- The coordinator relays requirements questions and the final delivery summary only.
Version History
- e0220ca Current 2026-07-05 23:31
