docs(prompts): add missing permissions-required to create-workflow field list - #2154
Draft
github-actions[bot] wants to merge 1 commit into
Draft
github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
…eld list Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
Azure Pipelines: 2 pipeline(s) were filtered out due to trigger conditions. There may be pipelines that require an authorized user to comment /azp run to run. |
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.
Agent Documentation Update
Findings
permissions-requiredis a real, documentedFrontMatterfield (src/compile/types.rs, serde renamepermissions-required; described indocs/imports.md#permissions-requiredanddocs/front-matter.md) used to declare abstract read/write capability requirements for reusable components, but the create-workflow authoring prompt's optional front-matter field checklist omitted it. Since this prompt drives theado-awagent's workflow-authoring output, an agent following it would never know to emitpermissions-requiredwhen scaffolding a reusable component, silently under-specifying its abstract capability contract.prompts/create-ado-agentic-workflow.mdApplied Fixes
permissions-requiredto the optional front-matter key list inprompts/create-ado-agentic-workflow.mdstep 2 ("Build Front Matter"), alongside the existingpermissionsentry.Notes
Verified
permissions-requiredagainstsrc/compile/types.rs(FrontMatter::permissions_required: PermissionsRequired,#[serde(rename = "permissions-required")]) and its documented semantics indocs/imports.md("## permissions-required" section) anddocs/front-matter.md. Checked open PRs via GitHub search first (is:pr is:open repo:githubnext/ado-aw permissions-required prompts create-ado-agentic-workflow) — no overlapping PR found. Other drift candidates found during the audit (e.g.container_runtime.rsmissing from theAGENTS.mdarchitecture tree, ecosystem-domain list drift,ir.mdstaleness) are already covered by multiple existing open PRs, so this run intentionally left those untouched to avoid duplicate work.Created by the agent-documentation maintainer workflow.