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
Rule
Requirement
Template skeleton
Read step template from references/ and replicate
Exact text
Use H2 text from templates verbatim
Exact order
Required H2s appear in the order listed
Anchor rule
Extra sections allowed ONLY after last required H2
No omissions
Every H2 listed must appear in output
Attribution
> Generated by {agent} agent | {YYYY-MM-DD}
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:
Mark your step as complete in ## ✅ Workflow Progress
Add artifact files to ## 📄 Generated Artifacts
Update Last Updated date and progress bar percentage
Placeholder Syntax
All templates use single-brace {placeholder-name} syntax:
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)
When generating a Step N artifact, read the corresponding template:
Reference
When to Load
references/01-requirements-template.md
Generating Step 1 requirements
references/02-architecture-template.md
Generating Step 2 assessment or Step 3 cost estimate
references/04-plan-template.md
Generating Step 4 plan, governance, or preflight
references/05-code-template.md
Generating Step 5 implementation reference
references/06-deploy-template.md
Generating Step 6 deployment summary
references/07-docs-template.md
Generating Step 7 workload documentation
references/styling-standards.md
Applying callouts, badges, emoji, navigation
references/cost-estimate-sections.md
Cost estimate H2 structure and formatting rules
Converted and distributed by TomeVault — claim your Tome and manage your conversions.
1---2name: jonathan-vella-azure-agentic-infraops-azure-artifacts3description: Azure Artifacts Skill4---56# Azure Artifacts Skill78Single source of truth for artifact template structures and styling.9Per-step H2 definitions live in `references/` — load only the step10you are generating.1112---1314## Artifact Generation Rules1516### Mandatory Compliance1718| Rule | Requirement |19| --------------------- | --------------------------------------------------- |20| **Template skeleton** | Read step template from `references/` and replicate |21| **Exact text** | Use H2 text from templates verbatim |22| **Exact order** | Required H2s appear in the order listed |23| **Anchor rule** | Extra sections allowed ONLY after last required H2 |24| **No omissions** | Every H2 listed must appear in output |25| **Attribution** | `> Generated by {agent} agent \| {YYYY-MM-DD}` |2627### DO / DON'T2829- **DO**: Read the step-specific template before generating30- **DO**: Copy H2 text character-for-character (including emoji)31- **DO**: Save all output to `agent-output/{project}/`32- **DON'T**: Reorder H2 headings from the listed sequence33- **DON'T**: Use placeholder text like "TBD" or "Insert here"34- **DON'T**: Add custom H2 sections BEFORE the last required H23536---3738## Mandatory: Project README3940Every project in `agent-output/{project}/` **MUST** have a41`README.md`.4243After saving step artifact(s), update the README:44451. Mark your step as **complete** in `## ✅ Workflow Progress`462. Add artifact files to `## 📄 Generated Artifacts`473. Update `Last Updated` date and progress bar percentage4849---5051## Placeholder Syntax5253All templates use single-brace `{placeholder-name}` syntax:5455- Lowercase, hyphen-separated: `{project-name}`, `{monthly-cost}`56- No Mustache/Handlebars `{{double-braces}}`5758---5960## Automated Validation6162```bash63npm run lint:artifact-templates # H2 order and required headings64npm run lint:h2-sync # Template ↔ artifact sync65npm run validate:all # All validators together66```6768---6970## Quality Checklist7172- [ ] H2 headings match template exactly (text + order)73- [ ] Attribution header present with agent name and date74- [ ] No placeholder text ("TBD", "Insert here", "TODO")75- [ ] File saved to `agent-output/{project}/` with correct name76- [ ] Collapsible TOC present (`<details open>` block after badge row)77- [ ] Cross-navigation table present (header with ⬅️ Previous / 📑 Index / Next ➡️)78- [ ] Mermaid diagram included (if template contains one)79- [ ] Traffic-light indicators used (✅ / ⚠️ / ❌ where template shows status columns)80- [ ] Collapsible `<details>` blocks present (if template contains them)8182---8384## Reference Index8586When generating a Step N artifact, read the corresponding template:8788| Reference | When to Load |89| ---------------------------------------- | ---------------------------------------------------- |90| `references/01-requirements-template.md` | Generating Step 1 requirements |91| `references/02-architecture-template.md` | Generating Step 2 assessment or Step 3 cost estimate |92| `references/04-plan-template.md` | Generating Step 4 plan, governance, or preflight |93| `references/05-code-template.md` | Generating Step 5 implementation reference |94| `references/06-deploy-template.md` | Generating Step 6 deployment summary |95| `references/07-docs-template.md` | Generating Step 7 workload documentation |96| `references/styling-standards.md` | Applying callouts, badges, emoji, navigation |97| `references/cost-estimate-sections.md` | Cost estimate H2 structure and formatting rules |9899---100> Converted and distributed by [TomeVault](https://tomevault.io/claim/jonathan-vella) — claim your Tome and manage your conversions.101<!-- tomevault:4.0:skill_md:2026-04-11 -->
Run npx skillmds@latest add tomevault-io/jonathan-vella-azure-agentic-infraops-azure-artifacts in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
Azure Artifacts Skill It is listed under DevOps & Infra on SkillMD.
This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.