Objective

Document the steps: pre-fetch artifact-staging pattern as a named, reusable example in the prompt library / documentation.

Context

From discussion #21704 (Agent Persona Exploration - 2026-03-19), the evaluation noted that the artifact-staging pattern — downloading CI artifacts in a steps: block before the agent starts — is non-obvious but essential for coverage/artifact workflows (S7 QA scenario scored 4.8/5.0).

This pattern deserves a named example so workflow authors can discover and apply it easily.

Pattern Description

steps:
  - name: Download coverage artifact
    uses: actions/download-artifact@v4
    with:
      name: coverage-report
      path: /tmp/coverage

Key properties:

• Pre-fetch happens in the steps: block, before the agent prompt runs
• Artifact names should be configurable (not hardcoded)
• Artifact content is untrusted input — should be treated accordingly

Approach

1. Find where named patterns/examples are stored (check skills/, docs/, create-agentic-workflow.md)
2. Add a "Artifact Pre-Fetch Pattern" section with:
   • A concrete example using actions/download-artifact@v4
   • Guidance on making artifact names configurable (avoid hardcoding coverage-report)
   • Security note: treat downloaded artifact content as untrusted input
3. Link this pattern from the trigger selection section (pair with workflow_run trigger)

Files to Modify

• The create-agentic-workflow.md prompt or equivalent pattern library
• Relevant docs pages if a patterns/examples section exists

Acceptance Criteria

• Pattern is documented with a complete, working example
• Artifact name is shown as configurable (not hardcoded)
• Security note about untrusted artifact content is included
• Pattern is linked from or co-located with the workflow_run trigger guidance

Generated by Plan Command for issue #discussion #21704 · ◷

• expires on Mar 21, 2026, 1:48 AM UTC