$ loading_
Create and maintain ADRs with checks, references, and planning support.
This skill appears to be a prompt-only workflow with no declared secrets, remote endpoints, or executable components, so overall risk is low. Some caution remains because the repository is open source but lacks a declared license and has limited visible adoption and maintenance signals.
The material and checks indicate that this skill requires no secrets or environment variables. The README only describes an ADR authoring workflow and does not ask for tokens, accounts, or other sensitive credentials, so direct credential exposure and abuse risk is low.
The system reports no remote endpoints and classifies this as prompt-only. Although the README mentions optional use of Microsoft docs or Azure pricing tools when available, that is only guidance about external tools and does not establish built-in data egress by this skill itself.
There is no installation script, executable, local process launch, or command execution instruction. The content is mainly an ADR decision/documentation workflow, so there is no evidence that the skill itself has code execution or system-level invocation capabilities.
The documentation only references normal in-project paths such as `docs/architecture/decisions/ADR-TEMPLATE.md` and ADR naming rules. It does not declare any mechanism to directly read, bulk scan, write, or exfiltrate local sensitive data.
A positive factor is that it comes from an open-source Microsoft repository on GitHub, so the source is auditable. However, the license is undeclared, the repo shows 0 stars, and maintenance status is unknown, leaving weaker community validation and upkeep signals; this warrants caution rather than high risk.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "adr-workflow" skill from askskill: 1. Download https://raw.githubusercontent.com/microsoft/devsquad-copilot/main/.github/plugins/devsquad/skills/adr-workflow/SKILL.md 2. Save it as ~/.claude/skills/adr-workflow/SKILL.md 3. Reload skills and tell me it's ready
Create an ADR for migrating file storage from local disks to Azure Blob Storage. Check for duplicate existing decisions, determine the appropriate ADR status, add relevant Microsoft documentation links, provide a rough Azure cost estimate, and validate completeness at the end.
A complete ADR draft with context, options, recommended status, reference docs, cost estimate, and completeness validation results.
Update this ADR based on the following progress: the solution completed a PoC, passed security review, and is planned for rollout next quarter. Determine whether the status should change from Proposed to Accepted, and check whether implementation impact, rollback plan, or cost notes are still missing.
An updated ADR with a status recommendation and a list of missing or corrective fields.
We plan to introduce Azure API Management. First check whether existing ADRs already cover the same or a similar decision; if they do, explain the differences and recommend reuse or a new ADR; if not, generate a new ADR draft and include relevant Microsoft documentation and an approximate cost range.
A duplicate analysis plus either a reuse recommendation or a new ADR draft with documentation sources and a cost range.
Before creating any ADR, check if an ADR already exists in the same domain.
If a Proposed ADR exists: recommend reviewing and accepting the existing one before creating a new one. If an Accepted ADR exists: if the decision has changed, use "Superseded by NNNN".
Options: [R] Review existing / [S] Supersede (create new ADR) / [C] Create separate (different domain).
If no existing ADR exists in the domain:
[A] Decision already made: ask for the final decision and options considered. Create with Accepted status (but recommend Proposed for team review).[B] Needs discussion: ask for options to consider. Create with Proposed status.Options preferably come from the user. Offer suggestions only if:
Never invent options from templates, generic READMEs, or placeholder content.
Microsoft Documentation (for decisions involving Microsoft/Azure services):
microsoft_docs_search to look up limits, SLAs, pricing tiers, comparisonsmicrosoft_docs_fetch for full content of relevant pagesAzure Cost Estimate (if Azure MCP Server is available):
azure/pricing when cost is a ranked priority or the user asks about pricingAzure Cloud Architect (if Azure MCP Server is available and the project deploys to Azure):
azure/cloudarchitect (design) for Azure architecture recommendationsazure/deploy (architecture diagram) for Mermaid topology diagram[S] Incorporate / [M] Modify first / [I] Ignoredocs/architecture/decisions/ADR-TEMPLATE.mdNNNN-domain.md (e.g., 0001-data-persistence.md)Before considering the ADR complete, verify:
If there are missing fields, request information from the user.
| Rationalization | Reality |
|---|---|
| "ADRs are overhead" | A 10-minute ADR prevents a 2-hour debate about the same decision six months later. |
| "The code is self-documenting" | Code shows what was built. It does not show why, what alternatives were rejected, or what constraints applied. |
| "We will document the decision later" | Decisions made without records get re-debated. Later never comes. |
| "Nobody reads ADRs" | Future agents read them to avoid re-deciding. Future engineers read them to understand context. |
| "This decision is obvious, no ADR needed" | Obvious decisions still have alternatives. Recording the reasoning prevents someone from proposing the discarded alternative later. |
Design and review software architecture diagrams for clearer, documentation-friendly visuals.
Create, switch, and verify Git branches before starting implementation work.
Initialize projects or verify and generate up-to-date SDD documentation templates.
Verify and create standard community and governance files for new projects.
Verify assignee, dependencies, priority, and capacity before starting a work item.
Systematically triage failures and fix broken builds or unexpected runtime issues.
Create or review ADRs to compare technologies and document design trade-offs.
Generate architecture docs, ADRs, and review outputs for software design decisions.
Analyze ADRs to extract risks, trade-offs, and improvement suggestions.
Guide users to co-author docs, proposals, and specs through iterative refinement.
Turn transcripts, text, and images into structured Azure DevOps work items.
Review implementation plans for gaps, assumptions, and sequencing before coding starts