SMARTY

Repeatable Azure DevOps support workflows for GitHub Copilot — named commands, consistent outputs, and a place to turn case work into reusable team knowledge.

Get Started

Run /start-here in Copilot Chat (or start-here in CLI/Claude Code) — it handles setup and shows you everything.

Workflows

Every workflow is a command you can type in chat. Each command maps to a .prompt.md file you can open and edit. Complex commands delegate to skills.

For visual workflow diagrams, see docs/workflow-diagrams.md.

Case work

Command	When to use it
/scope-case	New case — get the right first questions
/research-error	Have an error message — get causes and next steps
/analyze-data	Have logs, YAML, or config — get a summary
/generate-action-plan	Need a full investigation plan and customer response
/draft-reply	Know the answer — write back quickly
/request-data	Need diagnostic data from the customer
/check-status	Rule out a service issue first
/triage-case	Structured triage with gap analysis and next-action plan

Knowledge & docs

Command	When to use it
/review-devops-support-doc	Turn a solved issue into reusable team knowledge
/explain	Quick explanation of a term or concept
/capture-explanation	Publish a reusable explanation under docs/
/browse	Search docs, sources, scope-cases, skills

Sources & data

Command	When to use it
/add-source-intake	Bring new reference material into the workspace
/sanitize-for-copilot	Redact customer PII before using Copilot
/local-sources-only	Restrict analysis to local workspace material
/compare-versions	Compare two versions of a repo side by side

Learning & growth

Command	When to use it
/get-training	Training path or learning recommendation
/create-learning-project	Scaffold a structured learning plan

Navigation & meta

Command	When to use it
/start-here	First-run setup + full command index
/start-tour	Guided tours of every feature area
/log-session	Record session activity for later resume
/resume	Pick up where you left off
/feedback	Share feedback on a tour, prompt, or workflow

M365 integration

Command	When to use it
/work-iq-case-context	Pull M365 email/meeting context into a case
/work-iq-inbox-triage	Triage inbox for support items

Tours

Type /start-tour to see all guided tours, or jump directly:

Tour	Command	Time
Configuration	/start-tour-config	~5 min
Source Management	/start-tour-sources	~10 min
Core Commands	/start-tour-commands	~10 min
Triage Workflow	/start-tour-triage	~10 min
Reusable Knowledge	/start-tour-knowledge	~10 min
Learning & Training	/start-tour-learning	~10 min
Skills & Sharing	/start-tour-skills	~10 min
Data Sanitization	/start-tour-sanitization	~8 min
Real-World Capstone	/start-tour-capstone	~20 min

What's In The Repo

Path	What it is
.github/prompts/	The /commands you type in chat — one file per workflow
.github/skills/	Multi-step workflows behind complex commands
.github/instructions/	Workspace-wide rules (governance, collection ops)
docs/	Reusable docs the team publishes
docs/workflow-diagrams.md	Mermaid flowcharts for every major workflow
scripts/	Bootstrap and validation helpers
sources/	Local-only reference material (not tracked in git)

Skills

Skill	Version	What it does
add-source	1.0	Ingest and classify reference material into sources/
action-plan-to-analysis-doc	1.0	Turn action plans into Learn-style docs under docs/
browse-local-resources	1.0	List, search, describe workspace collections
compare-versions	1.0	Diff two git refs of a public repo
get-training	1.0	Recommend training paths and create training plays
learning-project-review	1.0	Score learning project completion evidence
learning-project-scaffold	1.0	Scaffold a structured learning project
local-wiki-action-plan	1.0	Action plan from local sources and wiki
pieman-sanitize	1.0	Redact PII with pieman CLI
triage-case	1.0	Structured triage with gap analysis
work-iq-triage	1.0	Enrich cases with M365 context
analyze-data	1.0	Detect data type, load analysis profile, produce structured summary

Scripts

Script	What it does
scripts/bootstrap-sources.ps1	Clone optional reference sources (agent, tasks, wiki)
scripts/check-protected-paths.ps1	Guard read-only paths from accidental edits
scripts/install-git-hooks.ps1	Wire up the pre-push validation hook
scripts/pre-push-validation.ps1	Structural checks that run before git push
scripts/check-workiq-prereqs.ps1	Verify Work IQ M365 prerequisites

Versioning

SMARTY tracks versions for artifacts that have downstream consumers (other prompts, skills, or users who depend on stable behavior).

What	Where	How
Skills	version: in SKILL.md frontmatter	Bump on behavior changes. Skills are the most change-sensitive — prompts and other skills depend on their contracts.
Prompts	version: in .prompt.md frontmatter	Bump when output format or rules change. Minor tweaks don't need a bump.
Instructions	version: in .instructions.md frontmatter	Bump on rule changes that affect all prompts or skills.
Sources	version: in _source-metadata.md	Track the upstream version or date the source was fetched.

Version format: major.minor — bump major for breaking changes (output format, removed steps), minor for additions or refinements.

Using SMARTY from the CLI

SMARTY works in VS Code Copilot Chat, the GitHub Copilot CLI (gh copilot), and Claude Code. The / prefix on commands is a VS Code-only convention — in any other environment, just type the workflow name as plain text.

Feature	VS Code Copilot Chat	GitHub Copilot CLI / Claude Code
Slash commands (/scope-case)	✅ Native	Not needed — type scope-case instead
Prompt files (.prompt.md)	Auto-loaded	Read on demand via AGENTS.md mapping
Skills (.github/skills/)	Auto-discovered	Read on demand when referenced
MCP servers (.vscode/mcp.json)	✅ Configured	Not applicable

The full command-to-file mapping is in AGENTS.md, which the CLI agent reads automatically.

More

• smarty-config.md.example: full shell manifest
• CONTRIBUTING.md: contribution and validation guidance
• SUPPORT.md: issue-reporting guidance
• SECURITY.md: security reporting guidance