Use this skill when the user wants the PRODUCT audited from the outside in — what the website promises vs what the code does vs what a real user experiences vs what actually arrives by mail vs what the data says is used. Runs a 7-role read-only wave (R5 writes only under an explicit SAFETY block) against a per-repo `.orchestrator/journey-manifest.md` and writes a dossier to docs/audits/. Distinct from /discovery, which checks code quality inside-out — this checks product truth outside-in; the...
Scanned 9/2/2026
Install to Claude Code
Skills Directorynpx -y skills add Kanevry/session-orchestrator --skill journey-audit --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Journey Audit?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/kanevry-journey-audit)More formats (shields.io, HTML) on the badges page.
---
name: journey-audit
description: "Use this skill when the user wants the PRODUCT audited from the outside in — what the website promises vs what the code does vs what a real user experiences vs what actually arrives by mail vs what the data says is used. Runs a 7-role read-only wave (R5 writes only under an explicit SAFETY block) against a per-repo `.orchestrator/journey-manifest.md` and writes a dossier to docs/audits/. Distinct from /discovery, which checks code quality inside-out — this checks product truth outside-in; they complement, neither replaces the other. Triggers \"journey audit\", \"Nutzersicht-Audit\", \"audit the product from the user's side\", \"/journey-audit\"."
disable-model-invocation: true
---
# journey-audit
Canonical skill: `skills/journey-audit/SKILL.md`
Read that file and follow it exactly. Resolve relative links against `skills/journey-audit/`, not this wrapper.
Cursor has no Skill tool. Treat "invoke the journey-audit skill" as: Read `skills/journey-audit/SKILL.md`.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
