agentic-workflow-suite

Execute an MCP/external-tool action with privacy gate, output validation, and audit trail

Run Review-Fix-Verify on a code change with separated phases and evidence requirement

Check whether a recurring pattern should become a real Skill (promote / keep-as-pattern / already-covered / reject)

Promote a raw inbox file (image, voice transcript, telegram note) into a curated wiki page

Run a dynamic-graph audit on a broad scope (plugin ecosystem, wiki cluster, repo monorepo)

Use when the user wants to turn a rough idea, screenshot, diagram, voice note, raw inbox file, or hand-drawn sketch into a concrete agentic workflow with triggers, inputs, steps, verification, error paths, and a Skill/Command/Hook/MCP recommendation. Trigger phrases - "design a workflow", "turn this into a skill", "make a blueprint", "spezifiziere", "mach daraus ein workflow", "skill blueprint", "/workflow design". Do NOT use this skill to execute workflows or write production code; the output is a blueprint, not an implementation. Also skip when the user only wants a diagram and is not asking for a runnable agentic process.

Use when work routes through DCO (Dynamic Central Orchestrator), Telegram bot, Mini-App, or MCP tools and crosses privacy/data classification boundaries. Trigger phrases - "dco safe run", "mcp action with validation", "telegram tool gate", "/mcp safe-run", "mit tool grenzen", "privacy gate". Validates tool output before persisting to DB/wiki/answer. Skip for purely local file edits without external tools and skip when no privacy class change is involved.

Use when a broad ecosystem (plugin landscape, wiki cluster, repo monorepo, DCO function map) needs an audit where the actual graph emerges through exploration, not from a pre-defined plan. Trigger phrases - "audit the plugin ecosystem", "schau dir alles an", "inventur machen", "find redundancies", "map the wiki", "/workflow audit", "ecosystem review". Returns inventory, clusters, role/dataflow map, redundancies, synergies, prioritized TODOs. Skip when the scope is small enough for a single-loop pass or when the audit was just done within the last 7 days.

Use when raw inbox material (image, voice transcript, telegram note, link) in wiki/raw/ should be promoted into a curated wiki page with proper frontmatter, sources, and cross-links. Trigger phrases - "curate this raw file", "promote raw to wiki", "kuratiere die raw datei", "ins wiki ueberfuehren", "raw inbox aufraeumen", "/wiki curate". The skill writes a NEW wiki page; the raw file stays untouched. Skip when the user wants only to read raw content without producing a wiki artifact, or when the source is not in wiki/raw/.

Use when a code change is risky enough that a linear patch is not safe — separates Review (find findings), Fix (apply minimal patch), and Verify (run tests/lints/UI checks) into distinct phases with feedback. Trigger phrases - "review-fix-verify", "review this patch", "kritischer review", "pruef das nochmal", "patch reviewen", "/review-loop". Each finding requires evidence (file:line, test, screenshot). Skip when the change is trivial or already verified, and skip when there is no test/verification surface (then prefer plain code-reviewer).

5 hooks across 3 events