azdo-issue skillB
azdo-issue is agent-read markdown (skill) from chan4lk/specclaw: Create or update an Azure Boards Work Item that mirrors this proposal. Targets Azure DevOps Boards (Features / User Stories / Tasks / Bugs / Epics) using the credentials from /specclaw:auth-azdo. Mirrors /specclaw:issue (Jira) and the GitHub Issues sync but for ADO Boards. Requires `azdo.boards.sync: true` in config.yaml..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# specclaw azdo-issue **First, run** `specclaw-ensure-init .specclaw` — idempotently creates `.specclaw/` if it doesn't exist (silent if already initialized; auto-inits using the current directory's basename as the project name). Create an Azure Boards Work Item from a specclaw change. Requires: - `proposal.md` to exist (run `/specclaw:propose` first). - `azdo.boards.sync: true` and a valid `azdo.boards.work_item_type` in `config.yaml`. - ADO credentials already set up via `/specclaw:auth-azdo`. ## Subcommands **Create the Work Item:** ```bash specclaw-azdo-issue create .specclaw <change> ``` Idempotent — if a Work Item already exists for this change (recorded in `status.md`), exits with a warning and does not duplicate. **Update the Work Item description with the latest task checklist:** ```bash specclaw-azdo-issue update .specclaw <change> ``` **Post a comment:** ```bash specclaw-azdo-issue comment .specclaw <change> "<comment text>" ``` **Close (final comment + closed-by-specclaw tag, no state transition):** ```bash specclaw-azdo-issue close .specclaw <change> ``` **Link a pull request to the Work Item:** ```bash …
Read the whole file at its exact version.
How to install
mdr add chan4lk/specclaw/azdo-issue@git:20260706.ade5fa1mdr add chan4lk/specclaw/azdo-issue@sha256:d7274fc03fa93b86Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_cijk46tvlrccf5md)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260706.ade5fa1 latest | 2026-07-06 | ade5fa1 | 2,318 B | B | view · diff |
| git:20260515.aec77ba | 2026-05-15 | aec77ba | 2,316 B | B | view |
Audit of the latest version
- fail: Frontmatter declares a name
- pass: Frontmatter block present
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (2318 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
chan4lk/specclaw · 12 stars · license MIT · pushed 2026-09-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_cijk46tvlrccf5md GET https://markdownregistry.com/api/v1/resolve?ref=chan4lk/specclaw/azdo-issue GET https://markdownregistry.com/api/v1/blob/d7274fc03fa93b861910d2992bd177bb5e73a212076b66940dd8c761b609bc8e
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.