Decomposed ticket workflow from the AI Native DevCon London 2026 context workshop: skills for code and documentation tickets, the mandatory tests-first / clean-review / human-review rules, and the deterministic scripts/ they lean on.
70
88%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Scope: documentation-only PRs (the documentation-ticket workflow) — changes
confined to the README, docs/, any .md file, or plain text/typo fixes, with
no source-code changes.
Prose is judged by people, not by a code reviewer. Therefore, for a docs PR:
scripts/request_copilot_review.py) on a documentation PR.If you are unsure whether a ticket is documentation or code, it is not a docs ticket — treat it as code and follow tests-first and merge-on-clean-review instead.