I'm trying to refine a workflow that first does planning and stores the plans in Azure DevOps (ADO). Then the coder skill will grab the ADO tasks, work on them, then update progress so the team can see what's going on. I've encorporated the use of grill-me developed by (Matt Pocock) [https://github.com/mattpocock/skills]
npx skills@latest add markrullo/CopilotAddons
/setup-verification-ado - this aims to verify the setup to ensure global and project instructions have already been provided.
/planner-ado - aims to use the grill-me skill with the added instruction of persisting the plan in ADO with the setup already provided by your config, breaking higher-level work down into executable tasks.
/coder-ado - aims to implement existing ADO work items, discover child tasks when a higher-level item is supplied, follow dependency order, ask for missing information instead of inventing it, and write progress back to ADO as it works.
These are some general global instructions that I have setup:
## Output Style
- Prefer concise responses
- Use bullet points or step-based format
- Summarize multiple options before details
- Stop after logical step when performing multi-step tasks
## Work Items (Azure DevOps)
- Always confirm organization/project if not known
- Store confirmed values in \docs\agents\issue-tracker.md
### Creation Rules
- Prefer: Feature → User Stories → Tasks
- Bugs should be created as Bug work items
- Link work items appropriately
### Quality Rules
- Title: concise and descriptive
- Description: must include:
- context
- expected outcome
- references (links, screenshots, work items)
### Completion Rules
- Update status
- Add comments summarizing work
- Link PRs / commits
- For bugs: include resolution details and follow-ups
## Guardrails
- Do NOT assume missing context — ask clarifying questions
- Do NOT generate code in planning mode
- Do NOT invent Azure DevOps structure — confirm when unsure