microsoft / microsoft/vscode-dotnettools
[P1][Tier 4] Add pilot gates and operational controls for new and bulk AI workflows
Open
Nobody has claimed this yet.
AIEngineering
- Dominant language
- No language data
- Stars
- 321
- Forks
- 54
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 2
Description
Tier 4 — FC-specific leverage · Priority: P1
Gap
There is no standard requirement to pilot new AI workflows on 3-5 real items before broad rollout, and no throttling/ownership/review-gate/rollback controls for bulk workflows.
Investment
- Require piloting new AI workflows on 3-5 real items with an owner and stop condition before broad rollout.
- Add throttling, ownership, review gates, and rollback/stop conditions for bulk workflows.
Acceptance criteria
- Pilot gate (owner, stop condition, review plan) documented for new AI workflows.
- Bulk workflows have throttling, review gates, and rollback/stop controls.
Part of epic #3273
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading epic #3273 and this issue's acceptance criteria to determine where AI workflow guidance and bulk-operation controls belong. Done means documenting a pilot owner, stop condition, and review plan, plus throttling, review gates, and rollback or stop controls for bulk workflows.
Written by the indexing model from the issue text.
Assessment
- Domain
- ai, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100