Determine the article type from structure and metadata:
- Concept/overview, How-to/guide, Tutorial, Reference, Architecture pattern
Check for MISSING standard sections expected for that type:
- Prerequisites (how-to/tutorial)
- Architecture diagram (architecture pattern/overview)
- Code samples (how-to/tutorial with technical steps)
- Next steps / Related content
- Limitations / Known issues / Considerations
- Pricing or cost considerations (for billable Azure services)
- Security considerations (for services handling data/auth)
- Monitoring / Observability (for deployed workloads)
Use microsoft_docs_search to search for related articles on the same topic — identify:
- Key scenarios covered by sibling articles but absent here
- Common customer questions the article doesn't address
- Alternative approaches or migration paths not mentioned
Check whether the article addresses multiple relevant personas:
- Developer, architect, operator/admin, security engineer
- Only flag if the article's scope clearly implies multiple audiences
Evaluate "Related content" / "Next steps" completeness:
- Are obvious companion articles missing?
- Does the article link to the service's main documentation hub?

What NOT to do

Suggest text edits, rewrites, or corrections (other skills own that)
Flag content that IS present — only what's ABSENT
Invent gaps for topics clearly outside the article's stated scope
Flag missing sections for article types that don't need them (e.g., don't demand code samples in a pure concept article)
Recommend adding entire new articles — stay within this document's scope

Output format

Report findings as:

If the article is structurally and topically complete, say so.