work-item-creation

Required Checklist

Before creating ANY work item, verify:

1. Platform: Read .memory/board-config.md to identify GitHub or Azure DevOps
2. Duplicates: Check if a similar work item already exists on the board
3. Required tags/labels: all present (see section below)
4. Title in correct format: see Title section
5. Body filled in: per the platform format (see GitHub and Azure DevOps sections)
6. Hierarchy: parent linked correctly
7. Durable descriptions: body describes behavior using domain language, not implementation details (see Durability Rules below)
8. Content style: title and body follow the Content Style section below

Content Style

Work items live on the board, get rendered in GitHub/ADO UIs, and are read by humans and agents long after creation. Apply these rules to every title, description, comment, and acceptance criterion.

These rules apply to content sent to GitHub Issues, Azure DevOps work items, board comments, PR descriptions written from a work item, and triage artifacts. They do not replace the markdown rules in the documentation-style skill, which still govern files under docs/**/*.md.

AI Model Traceability

All generated work items must include the tag/label ai-model:<model-name>.

How to identify the model in use

1. Try reading Copilot CLI logs:

   grep -h "Using.*model" ~/.copilot/logs/*.log 2>/dev/null | tail -1
   

2. If not found, check config:

   cat ~/.copilot/config.json 2>/dev/null | grep -i model
   

3. If unable to identify, ask the user
4. Last resort: use ai-model:unknown

Required Tags/Labels (every work item)

Auto-creation of Labels (GitHub)

Before applying labels to a work item, check if they exist in the repository:

github/list_label(owner, repo)

If any required label does not exist, create it automatically via github/label_write:

…