Menu
Deprecated — merged into m-worktree. Use m-worktree.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Audit a Jira or Azure DevOps board against ways-of-working rules, produce a tagged cleanup plan, then on one confirm gate apply safe bulk fixes and delegate epic/story/subtask creation to sibling skills. Triggers: audit my board, board audit, ado board audit, jira audit, audit board, backlog cleanup, board hygiene, board health, clean up jira, sprint cleanup, iteration cleanup, sprints used as epics, hidden tickets, fix backlog, organize backlog, epic story audit, backlog triage.
Shared board-provider layer — detect whether this session talks to Jira or Azure DevOps (ADO), load the matching provider mapping (tool names, query language, types, states), and record the choice in the calling skill's config.json. Board-facing skills delegate their provider detection here and stay platform-neutral. Triggers: which board provider, board setup, connect jira, connect ado, azure devops setup, board provider.
Author a new Claude Code skill — folder + SKILL.md + frontmatter, lean 50–120 lines, grounded in the host project's real files and conventions, integrated with sibling skills. Triggers: create skill, new skill, add skill, write skill, skill for, author skill, scaffold skill.
Standalone task orchestrator — take a request (or a board ticket) from GO gate through implement → test → verify → review → finalize by delegating to sibling m-skills. Works with or without an SDD spec. Triggers: implement, build, create feature, add feature, new screen, new page, task, scaffold, build X, ship this ticket, work on this ticket, do the ticket.
PM ticket authoring at the right altitude — turn a bug report, feature ask, or an over-technical draft into ONE clean ticket/work item that stops at Problem, Impact, Reproduction, and Acceptance Criteria, stripping engineering diagnosis (root cause, code, file:line, commit hashes, proposed fix) and leaving it to engineering. Works against Jira or Azure DevOps via the m-board provider layer; creates the ticket only after a confirm gate. Triggers: write a ticket, pm ticket, create work item, ado ticket, jira ticket, bug ticket at the right altitude, de-technify this ticket, file a bug, report a bug, raise a ticket, bug report, feature request, my ticket is too technical, clean up this ticket, acceptance criteria, problem impact reproduction, ticket too engineering-heavy.
QA deliverable generator — produce test plans, manual test cases, regression suites, design-vs-implementation validations, and structured bug reports from a feature description, in Markdown ready for any tracker. Optional Figma MCP integration for pixel-level design validation. Triggers: test plan, test cases, regression suite, QA, bug report, figma validation, manual testing, smoke test, test coverage.
| name | m-using-git-worktrees |
| description | Deprecated — merged into m-worktree. Use m-worktree. |
This skill has been merged into m-worktree. Use the m-worktree skill instead — it covers isolation detection, native harness tools, worktree creation, bootstrap, baseline tests, and cleanup handoff.
