Stats
Actions
Available In
Tags
Plugin
Dev Workflows
General-purpose development workflow skills. Ships grill-then-plan (domain-aware grilling that sharpens terminology, captures decisions inline as CONTEXT.md/ADRs, then hands off to the superpowers planning pipeline) and problem-description (generate interactive step-by-step HTML walkthroughs that explain a complex technical problem with concrete data). More skills to come.
What's Inside
Skills2
grill-then-plan
/grill-then-plan
Like grill-with-docs (domain-aware grilling, glossary sharpening, inline CONTEXT.md/ADR capture) BUT continues into the superpowers planning pipeline by handing off to superpowers:writing-plans at the end. Use ONLY when the user wants both the grilling AND a written implementation plan produced afterward; if they want grilling/docs alone, use grill-with-docs instead. Requires the superpowers plugin.
problem-description
/problem-description
Use when the user wants an interactive step-by-step HTML walkthrough explaining a complex technical problem (DB error, race condition, design issue, conceptual blocker) using concrete data and manual navigation. Triggers on phrases like "make me a walkthrough", "explain step by step with data", "interactive explanation", "make an animation", "walk me through with real examples", "อธิบายแบบ step by step", "ทำ animation/walkthrough/visualization", "ทำเป็น diagram", "วาด diagram". Do NOT use for one-line clarifications, conceptual Q&A answerable in a paragraph, or simple "what does X mean" questions — only when an interactive HTML artifact would clearly help.
README
Workflow Daily Work — Claude Code marketplace
A Claude Code plugin marketplace for daily-work automation. Today it ships one plugin:
ado-backlog— turn findings from any input (an Excel/CSV audit, a doc, a code/QA review, a pasted list of issues) into an Azure DevOps backlog: extract → triage → classify by your project's process → dry-run → create on approval → write ticket links back to the source. Each step is its own reusable skill, plus a one-shot orchestrator.
Install (each colleague, once)
Prerequisites: Claude Code, Azure CLI (az login),
.NET 10 SDK, Python 3 + openpyxl (pip install openpyxl).
# in Claude Code:
/plugin marketplace add ThodsaphonSonthiphin/workflow-daily-work
/plugin install ado-backlog@workflow-daily-work
# then sign in to Azure DevOps and check your setup:
az login
/ado-backlog:setup-check
CLI equivalents:
claude plugin marketplace add ThodsaphonSonthiphin/workflow-daily-workandclaude plugin install ado-backlog@workflow-daily-work. For team-wide install, add--scope project(writes to.claude/settings.json).
Use it
/ado-backlog:run "C:\path\to\your-findings.xlsx"
Answer the prompts (column mapping, which severities, who to assign to), approve the dry-run, and it creates the work items and writes the ticket links back into your file. Nothing is created in Azure DevOps until you approve the dry-run.
See plugins/ado-backlog/README.md for the full toolkit and
plugins/ado-backlog/QUICKSTART.md for the one-page cheat sheet.
Repo layout
.claude-plugin/marketplace.json # this marketplace (lists ado-backlog)
plugins/ado-backlog/
├── .claude-plugin/plugin.json
├── skills/ # 7 skills (each invocable as /ado-backlog:<name>)
├── commands/ # /ado-backlog:run, /ado-backlog:setup-check
├── scripts/ # create-backlog.cs, read_source.py, tracking.py, setup_check.ps1
├── references/data-contracts.md # the JSON shapes that connect the steps
├── examples/ # sample findings + backlog_input
├── README.md
└── QUICKSTART.md
Stats
Version0.2.0
LanguageHTML
Stars0
MaintenanceGood
LicenseMIT
Last Commit
Added
Available In
Tags
