菜单
Log a manual note about the dev-workflows plugin itself — friction you hit or an improvement you want — to the per-VI feedback file in the specs repo, for the plugin maintainer to aggregate. Tied to no command; run any time. Activated when the user prompt starts with "feedback:".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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.
| name | feedback |
| description | Log a manual note about the dev-workflows plugin itself — friction you hit or an improvement you want — to the per-VI feedback file in the specs repo, for the plugin maintainer to aggregate. Tied to no command; run any time. Activated when the user prompt starts with "feedback:". |
| allowed-tools | view, edit, create, bash, glob, grep, ask_user |
Log session feedback about the dev-workflows plugin: the argument (text following the feedback: trigger)
feedback: captures a manual note about the dev-workflows plugin itself —
friction you hit, or an improvement you want — and persists it per-VI into the
specs repo so the plugin maintainer can aggregate feedback across engineers. It
is tied to no command and can be run any time. You author the prose; the
command fills the metadata and writes the entry. origin: manual.
This command captures signal about the plugin, not about your target
project. Target-project tooling advice does not belong here (see
~/.copilot/installed-plugins/ihudak-copilot-plugins/dev-workflows/skills/_shared/feedback-emission.md §4).
feedback: argument is empty, ask the user for the note (the friction and the
improvement they want). Do not guess.Resolve, then confirm with the user in one grouped prompt (last choice always
"Other… (describe)"):
command — the exact command keyword this note is about (e.g. specify:), inferred from
recent context; or n/a if it is not about a specific command. Confirm.category — inferred from the controlled vocab in
~/.copilot/installed-plugins/ihudak-copilot-plugins/dev-workflows/skills/_shared/feedback-emission.md §1
(missing-capability, wrong-output, ambiguous-prompt,
missing-reference-doc, model-routing, manual-workaround,
false-positive, docs-ux, other); reuse an existing value when it fits.
Confirm.impact — blocker | friction | polish.author — git config user.email run in the specs repo (best-effort;
unknown if unset).plugin_version — read from
~/.copilot/installed-plugins/ihudak-copilot-plugins/dev-workflows/.plugin/plugin.json.Also resolve jira_key (from recent context, or null) and source
(vault | directory | none).
Cite ~/.copilot/installed-plugins/ihudak-copilot-plugins/dev-workflows/skills/_shared/feedback-emission.md and call its
emit-manual entry point (§6): resolve the write target via the §2 specs-first
ladder using jira_key and source, format the entry per §1 (origin: manual), and append per §3 (manual entries are never silently skipped — on an
id collision append a numeric suffix and warn). Write silently.
Surface the persisted path and any degradation notice (e.g. the tier-3 vault warning, or tier-5 report-only). This command NEVER commits, and NEVER writes into a docs/code repo or the current working directory.