Update AI Team Orchestration with risk-based delivery v2 🤖🤖🤖#2279
Open
denis-a-evdokimov wants to merge 2 commits into
Open
Update AI Team Orchestration with risk-based delivery v2 🤖🤖🤖#2279denis-a-evdokimov wants to merge 2 commits into
denis-a-evdokimov wants to merge 2 commits into
Conversation
github-actions
Bot
added
agent
Contributor
🔒 PR Risk Scan ResultsScanned 16 changed file(s).
|
Contributor
🔍 Vally Lint Results
Summary
Full linter output |
Contributor
Author
|
Automated risk-scan triage: the single medium |
Contributor
There was a problem hiding this comment.
Pull request overview
Updates AI Team Orchestration to a risk-based v2 delivery workflow.
Changes:
- Adds frozen-candidate, evidence-binding, and scoped-reopen processes.
- Introduces canonical delivery and Safe Git references.
- Updates agents, plugin metadata, and generated indexes.
Reviewed changes
Copilot reviewed 16 out of 16 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
agents/ai-team-dev.agent.md |
Defines Dev lifecycle and boundaries. |
agents/ai-team-producer.agent.md |
Adds risk-based gate orchestration. |
agents/ai-team-qa.agent.md |
Adds optional candidate-bound QA. |
skills/ai-team-orchestration/SKILL.md |
Updates the skill workflow. |
skills/ai-team-orchestration/references/anti-patterns.md |
Documents delivery anti-patterns. |
skills/ai-team-orchestration/references/brainstorm-format.md |
Clarifies simulated perspectives. |
skills/ai-team-orchestration/references/delivery-workflow.md |
Adds the canonical delivery lifecycle. |
skills/ai-team-orchestration/references/project-brief-template.md |
Adds delivery governance sections. |
skills/ai-team-orchestration/references/safe-git-values.md |
Adds validated Git procedures. |
skills/ai-team-orchestration/references/sprint-plan-template.md |
Adds risk, gate, and evidence fields. |
plugins/ai-team-orchestration/README.md |
Documents v2 usage. |
plugins/ai-team-orchestration/.github/plugin/plugin.json |
Updates metadata to v2.0.0. |
.github/plugin/marketplace.json |
Regenerates marketplace metadata. |
docs/README.agents.md |
Updates generated agent entries. |
docs/README.plugins.md |
Updates the plugin index. |
docs/README.skills.md |
Updates the skill and reference index. |
Comment on lines
+48
to
52
| │ │ │frozen /│ │planned │ | ||
| │ <working-│ │candidate/│ │branch │ | ||
| │ branch> │ │immutable│ └────────┘ | ||
| │ │ │preview │ | ||
| └──────────┘ |
| > | ||
| > First: git pull origin main && git checkout -b feature/sprint-N | ||
| > Start with a branch preflight. Run each step separately: | ||
| > 1. Run `git status --short`. If it reports changes, stop and preserve them; do not reset or stash unknown work. |
| cd <folder-name> | ||
| git checkout -b <branch-name> | ||
| npm install | ||
| git status --short |
| ### Validate names and branches | ||
|
|
||
| ```text | ||
| git status --short |
| After every candidate file is committed and all final Dev checks pass, verify that the worktree is still clean, the effective destination and current branch still match the plan, and the branch ref is a commit. The `rev-parse` output is the full tested local Candidate ID; capture it before the immediately following push. Do not edit or commit between capture and push. | ||
|
|
||
| ```text | ||
| git status --short |
| ### Fetch and verify the base | ||
|
|
||
| ```text | ||
| git fetch --prune BASE_REMOTE |
| git branch --show-current | ||
| git rev-parse --verify --end-of-options refs/heads/WORKING_BRANCH | ||
| git cat-file -t refs/heads/WORKING_BRANCH | ||
| git push --set-upstream PUSH_REMOTE refs/heads/WORKING_BRANCH:refs/heads/WORKING_BRANCH |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pull Request Checklist
npm startand verified the generated marketplace/docs outputs are up to date.mainbranch for this pull request.Description
Updates the existing AI Team Orchestration plugin to the canonical v2 risk-based delivery workflow:
ai-team-dev,ai-team-producer, andai-team-qaIDs while intentionally omittingtoolsandmodelThe managed content was exported one way from the merged canonical repository using its verified non-mutating patch-preparation flow.
Type of Contribution
Validation
0108a72a27fac358b3b3e65442f3beceecd35d3b30472ecf0fe34cc561df958c08501ecc5ca80ea4f149776ce1e561b03c69b6ca223f6f6d4c8fe256npm run validate: PASSnpm test: PASS, 99/99npm run skill:validate: PASSnpm run plugin:validate: PASSnpm start: PASSgit diff --check: PASSAdditional Notes
This supersedes closed PR #2275 with a fresh branch based directly on current
upstream/main. The plugin version remains2.0.0because v2 was not published by the closed PR. Independent review, QA, and smoke checks are intentionally risk-selected rather than universally mandatory; high-risk changes still require applicable security evidence or explicit maintainer risk acceptance.By submitting this pull request, I confirm that my contribution abides by the Code of Conduct and will be licensed under the MIT License.