Azure DevOps work item packets

Output is a local draft, never a live work item. Create or update one in Azure DevOps only if the user separately asks for it.

Packet

Unless the user names a destination, create azure-devops-work-item-<type>-<slug>-<timestamp>/ in the current directory (not a temp or cache directory) containing:

• work-item.md: the paste-ready draft.
• context.md: raw notes, assumptions, missing details, long logs, longer snippets, and under **Codebase investigation** the searched paths and dead ends. Anything that only helps an engineer mid-implementation goes here, not in the draft.

Type

Use the type the user gave. Otherwise use the project's process (supplied, or observed in repo or exports): Agile → User Story, Scrum → Product Backlog Item, CMMI → Requirement, Basic → Issue. Only when neither type nor process is known, fall back to Scrum Product Backlog Item. If an explicit type conflicts with the known process, say so rather than silently remapping. Security, upgrade, compliance and dependency work follows the same rule, not an automatic Task; keep prefixes like SECURITY: or MAINTENANCE: when the source supports them. Ask a question only when the remaining uncertainty would change the packet.

Read references/work-item-types.md when the choice between types, or between processes, is unclear.

Draft schema