Skip to content

update-ado-agentic-workflow.md

Latest commit

 

History

History
69 lines (56 loc) · 2.49 KB

update-ado-agentic-workflow.md

File metadata and controls

69 lines (56 loc) · 2.49 KB
Raw

Update an Azure DevOps Agentic Workflow

Apply the shared prompt contract before executing this prompt: https://raw.githubusercontent.com/githubnext/ado-aw/main/prompts/prompt-contract.md

Core

Role

Apply requested changes to an existing ado-aw workflow source file with minimal, targeted edits.

Constraints

  • Read the entire source file before editing.
  • Modify only requested behavior.
  • Preserve unrelated structure and intent.
  • For model defaults, follow src/engine.rs (DEFAULT_COPILOT_MODEL) instead of hardcoding prompt-local defaults.
  • Do not perform external side effects without explicit user consent.

Output Format

  1. Updated .md content.
  2. Change summary by field/body section.
  3. Recompile requirement and next steps.

Task Module: Update

1. Baseline Current State

Identify current:

  • front matter keys,
  • safe-outputs + permissions,
  • mcp-servers/tool allow-lists,
  • trigger/schedule settings,
  • instruction body structure.

2. Apply Targeted Changes

  • Touch only requested keys/sections.
  • Keep front-matter ordering stable when practical.
  • If changing on.pr branch/path filters, ensure mode choice (synthetic vs policy) is explicitly considered.

3. Validate

Run a compact checklist:

  • requested changes fully applied,
  • no accidental privilege expansion,
  • no contradictory instructions,
  • no invalid safe-output references,
  • recompilation need correctly determined.

Recompile rule:

  • front matter changed -> ado-aw compile required,
  • body-only changes -> compile only if inlined-imports: true.

4. Return Result

Return:

  • concise diff summary,
  • whether compile is required,
  • next steps:
    1. review updated .md,
    2. if required run ado-aw compile <path/to/file.md>,
    3. commit changed files.

Done Criteria

  • The requested behavior is fully applied with no unrelated changes.
  • Existing structure, permissions, and intent are preserved unless the request requires changing them.
  • The updated source is internally consistent and uses only valid safe outputs.
  • Recompilation guidance matches the actual changed surface and inlined-imports setting.

References