ihudak

Jira-driven release-notes drafting. Reads a Value Increment (or any ticket) from exported markdown, optionally grounds in PR diffs, renders a dynatrace-docs release-notes body, runs a light dt-style-checker gate, and writes a persistent draft to paste into Jira's release-notes field. Activated when the user prompt starts with "release-notes:".

Architecture-authoring workflow (Product Architect phase, sub-project 3 of the VI-creation flow). Grounds on the mounted implementation repos (architect-driven discovery — no PRs) and authors an ARD for a VI (create-ard: <VI-KEY>) or an Epic (create-ard: <VI-KEY> <Epic-KEY>, inheriting the VI-level ARD), against _shared/ard-format.md, gated by the Opus ard-reviewer, written to $SPECS_PATH/specifications/<KEY>-<slug>/. Optional; scoped; product-architecture level (no code writing). Introduces the pa role. Activated when the user prompt starts with "create-ard:".

VI-creation workflow (PM phase, sub-project 2 of the VI-creation flow). Turns a refined idea.md + a user-supplied JIRA-KEY into a high-quality Value Increment document (spine + adapt-in profiles: --lean|--hybrid|--full), authored via a relentless grill against _shared/vi-format.md, gated by the Opus vi-reviewer, written to $SPECS_PATH/specifications/<KEY>-<slug>/ and published to Jira by paste + re-import. Product-level (no code scan). Offers release-notes: and create-ard: as next steps. Activated when the user prompt starts with "create-vi:".

VI-update workflow (PM phase) — refresh/re-do an existing Value Increment. Resolves the VI Jira-import-first (source of truth) with a 3-day freshness gate, grounds on the VI + comments + any ARD/spec/transcript, updates it via a relentless grill against _shared/vi-format.md, gated by the Opus vi-reviewer, and writes canonical + archived revisions to $SPECS_PATH/specifications/<KEY>-<slug>/. Product-level (no code scan). Activated when the user prompt starts with "update-vi:".

Jira-driven feature-documentation workflow. Phase 0 preflight-discovers the docs repo + profile (in-repo → built-in dynatrace-docs default → on-demand docs-profile:) and the VI's specs dir under /workspace. Phase 4.5 determines/confirms the applicable space(s). Optional saas|managed constraint scopes the run to one space. Reads a Value Increment hierarchy from exported markdown, resolves PR diffs in parallel, synthesises product documentation, and gates on style-check and Opus doc review. Optional --counterpart <JiraID|PR-url> grounds a space-constrained run on the other space's existing docs (read-only). Activated when the user prompt starts with "document:".

Scan the vault (or a target directory) for tags used in page frontmatter and page bodies, diff against the vault's .obsidian/copilot/tag-index.md, prompt the user to approve new tags and clean stale ones, then update tag-index.md in place. Run after heavy ingest or other large content changes when new concepts may have introduced new tags. Triggers on: wiki-tags-refresh, refresh tags, update tag index, wiki tags, sync tags.

Initialize or re-initialize vault integration for the LLM wiki pattern. Creates .raw/ inbox, bootstraps wiki/ with skeleton files (_index.md, _log.md, _manifest.json, hot.md), syncs wiki-schema and task-creation-rules to .obsidian/copilot/, bootstraps tag-index.md if absent, and merges wiki blocks into CLAUDE.md and .github/copilot-instructions.md. Safe to re-run after plugin updates — existing wiki pages are never touched, skeleton files are never overwritten. Triggers on: wiki-init, initialize the wiki, set up the wiki, bootstrap the wiki, init wiki, wiki setup, wiki initialize, set up obsidian-llm-wiki.

Jira-driven Epic-writing workflow. Reads a Value Increment and existing Epics from exported markdown, optionally scans code repos, drafts child Epic definitions, and gates on dt-style-checker and Opus epic-reviewer. Activated when the user prompt starts with "epics:".

Create a single Obsidian Tasks-compatible task from a natural language prompt. Detects target file, tags, Fibonacci effort estimate, priority, scheduled/due dates, Jira links, and people references. Previews the formatted task for user approval before inserting. Replaces the legacy "task:" prefix. Triggers on: wiki-task, create task, add task, new task.

Initialize or re-initialize vault integration for the LLM wiki pattern. Creates .raw/ inbox, bootstraps wiki/ with skeleton files (_index.md, _log.md, _manifest.json, hot.md), syncs wiki-schema and task-creation-rules to .obsidian/copilot/, bootstraps tag-index.md if absent, and merges wiki blocks into CLAUDE.md and .github/copilot-instructions.md. Safe to re-run after plugin updates — existing wiki pages are never touched, skeleton files are never overwritten. Triggers on: wiki-init, initialize the wiki, set up the wiki, bootstrap the wiki, init wiki, wiki setup, wiki initialize, set up obsidian-llm-wiki.

Vault knowledge schema for the obsidian-llm-wiki plugin. Defines the three-layer source model, page types, frontmatter schemas, tag rules, cross-linking conventions, and the format of _index.md, _log.md, _manifest.json, and hot.md. Read this before any wiki operation (ingest, scan, query, save, lint, hot, tags-refresh). Triggers on: wiki schema, wiki conventions, wiki structure, wiki rules.

Scan the vault (or a target directory) for tags used in page frontmatter and page bodies, diff against the vault's tag-index.md, prompt the user to approve new tags and clean stale ones, then update tag-index.md in place. Run after heavy ingest or other large content changes when new concepts may have introduced new tags. Triggers on: wiki-tags-refresh, refresh tags, update tag index, wiki tags, sync tags.

Load the dev-workflows task-complexity classification rules and model fallback chain. Invoked at the classification step by the 13 pipeline commands (`/implement`, `/document`, `/epics`, `/release-notes`, `/vuln`, `/upgrade`, `/docs-profile`, `/idea`, `/create-vi`, `/create-ard`, `/specify`, `/design`, `/ready`), because slash-command bodies cannot expand ${CLAUDE_PLUGIN_ROOT} themselves.

Apply dynatrace-docs frontmatter conventions — changelog entries and managed-docs owners — when creating or editing documentation pages under dynatrace/_content/** or managed/_content/** in the dynatrace-docs repository. Use whenever you change a Dynatrace documentation page's content or frontmatter, or when the user mentions changelog, page owners, or dynatrace-docs frontmatter.

Dynatrace corporate style guide rules for writing Epics, PRDs, ARDs, product documentation, and other planning documents. Load this skill when writing or editing content that must follow Dynatrace terminology, trademarks, voice/tone, and formatting standards. Triggers on: Dynatrace style, DT terminology, write epic, write PRD, write ARD, Dynatrace content, style guide, corporate writing.

Batch-extract tasks from a wiki knowledge base. Harvests explicit action-item flags from _log.md and performs a semantic scan of wiki pages for implicit action items. Deduplicates against existing tasks, presents candidates for approval, and creates them using wiki-task format rules. Invoke after wiki-ingest or wiki-scan has processed meeting transcripts or documents. Triggers on: wiki-tasks-extract, extract tasks from wiki, harvest tasks, find action items.

Automatically fix security vulnerabilities by updating affected dependencies. Triggered by the "vuln:" command followed by space-separated tokens. Each token is either JIRA-ID:VULN-ID (e.g. MGD-2423:CVE-2023-46604) or a bare VULN-ID (e.g. CVE-2023-46604) when no Jira ticket exists. Handles CVE IDs automatically by looking them up on NVD. Skips CWE and OWASP IDs with a warning. For each CVE: fetches the affected library, checks if it is used in the repo, finds the minimal safe version, runs baseline tests, applies the fix, rebuilds, re-runs tests, then commits to a new branch and opens a pull request. Use when the user wants to remediate one or more security vulnerabilities in the current repository.

Upgrade one or more components (libraries, frameworks, languages, build tools, CI/CD actions) in the current repository to a target version. Triggered by the "upgrade:" command followed by space-separated tokens in the form "component:version", "component:minor", "component:latest", "component:lts", or bare "component" (latest compatible assumed). Works on any project regardless of language or ecosystem. Upgrades are applied to the current branch with no commits or PRs. Runs tests before and after each upgrade; updates test code if required by the new version. Use when the user wants to keep dependencies, frameworks, languages, or CI/CD actions current.

Use Atlassian CLI (acli) to manage Jira Cloud work items: authenticate, search/fetch tickets by project and status, update/edit fields, transition status, assign, comment, and perform safe bulk operations with JQL. Trigger this skill when the user asks to list Jira tickets, change status, edit issues, or automate Jira workflows via acli.

Investigate GitHub repositories using the gh CLI. Analyze PRs, issues, commits, CI/CD status, repo health, contributor activity, security vulnerabilities, and fetch repo docs/content. Use for any GitHub-related investigation or documentation retrieval.

Search, create, and manage notes in the Obsidian vault with wikilinks and index notes. Use when user wants to find, create, or organize notes in Obsidian.