Azure Artifacts Skill

Single source of truth for artifact template structures and styling. Per-step H2 definitions live in references/ — load only the step you are generating.

Artifact Generation Rules

Mandatory Compliance

DO / DON'T

• DO: Read the step-specific template before generating
• DO: Copy H2 text character-for-character (including emoji)
• DO: Save all output to agent-output/{project}/
• DON'T: Reorder H2 headings from the listed sequence
• DON'T: Use placeholder text like "TBD" or "Insert here"
• DON'T: Add custom H2 sections BEFORE the last required H2

Mandatory: Project README

Every project in agent-output/{project}/ MUST have a README.md.

After saving step artifact(s), update the README:

1. Mark your step as complete in ## ✅ Workflow Progress
2. Add artifact files to ## 📄 Generated Artifacts
3. Update Last Updated date and progress bar percentage

Placeholder Syntax

All templates use single-brace {placeholder-name} syntax:

• Lowercase, hyphen-separated: {project-name}, {monthly-cost}
• No Mustache/Handlebars {{double-braces}}

Automated Validation

npm run lint:artifact-templates   # H2 order and required headings
npm run lint:h2-sync              # Template ↔ artifact sync
npm run validate:all              # All validators together

Quality Checklist

• H2 headings match template exactly (text + order)
• Attribution header present with agent name and date
• No placeholder text ("TBD", "Insert here", "TODO")
• File saved to agent-output/{project}/ with correct name
• Collapsible TOC present (<details open> block after badge row)
• Cross-navigation table present (header with ⬅️ Previous / 📑 Index / Next ➡️)
• Mermaid diagram included (if template contains one)
• Traffic-light indicators used (✅ / ⚠️ / ❌ where template shows status columns)
• Collapsible <details> blocks present (if template contains them)

Reference Index

When generating a Step N artifact, read the corresponding template: