Draw and inspect user journeys on an editable native canvas, with optional release details, evidence checks, and portable tldraw or PNG exports.
Plugin kc-journey-map from marketplace kc-claude-plugins in iamcxa/kc-claude-plugins. Commands read from the repo's manifest — 2 days ago.
kc-journey-mapDraw or check a user journey, prepare a selected release for development, accept a built release by walking it end to end once every story's tasks are done (pending delivery acceptance), add one deferred story to an existing journey, add an editable Mermaid sequence companion, or answer architecture
kc-journey-progressUse when explicitly refreshing release story development progress or reporting remaining stories and pull requests after an archive with --report, optionally drawing the observation on the journey canvas. Drawing alone uses kc-journey-map.
Browser & CLI E2E testing pipeline with context-isolating subagents — map UI, generate flows, verify & test, walk through apps, record video, terminal recording for CLI-only flows, static UI computed-style verification
11 skills · 8 agents · hooks
Development workflow run by Spacedock, with profile principles, stage skills, advisory roles, an observer and optional extensions.
12 skills · 4 agents
PR lifecycle workflow — create (ship chain), review (incl. Trail of Bits security subagents + 5 pr-review-toolkit agents covering correctness/comments/silent-failure/type-design/test-coverage, optional Codex cross-model second opinion, cross-file doc-claim verification, per-agent 1-10 confidence calibration), resolve review threads with cross-review verdict persistence (suppress prior-dismissed findings across review cycles), commit reorg, announce, and automated daemon
7 skills · 3 agents · hooks
Team operations pipeline — EM triage with strategic lens (depth-adaptive routing, team context cache), project pulse updates, codebase exploration, issue decomposition, structured Linear management, EM plan/project review (keystone verification + cross-model pressure-test), and on-demand cross-model second opinion via Google's agy / Antigravity CLI (/gemini review|challenge|consult)
7 skills · 3 agents
No longer maintained; use kc-dev-flow-2. Profile-native POC, Pilot, and Production delivery routes that load one minimal authority core plus only the selected stage contract in Claude Code or Codex
6 skills · 2 agents
Session lifecycle & context efficiency — context pressure detection, cleanup enforcement, cross-session handoff/resume, MCP context firewall, context lake cache, journal with vector search, and statusline with usage quota
4 skills · 1 agent · 1 MCP server · hooks
Run a user story mapping workshop with adaptive questions and structured output.
1 skill
User research skills for designers: personas, empathy maps, journey maps, interview scripts, usability testing, card sorting, behavioural analytics, and reconciling data with research.
14 skills · 4 commands
Reuse tested app journeys with code, design and integration checks.
3 skills
A design-foundations system with a four-stage workflow (research → plan → mock → build). Design doctrine is loaded deterministically by Read() via a name→path resolver — six domains (content-design, behavioral, journey, deceptive-patterns, design-systems, ai-native) live as reference files in references/; two de-triggered skills (usability, data-viz) and two workflow skills (clarify, prototype) complete the plugin. The design-DNA pipeline grounds every candidate in two named references, then deals a seeded layout-first composition (scripts/dealer.mjs) — any axis user-pinnable — ahead of a criteria-bound critique and synthesis pass. Commands take any design idea from brief to viewable, gated artifact: research, plan, mock (sign-off gate), build (per-phase BUILD → REVIEW → commit). Review is dual-blind: an isolated cross-pillar critique and a deterministic detector (scripts/detect.mjs) gather findings independently and synthesize only after both finish.
4 skills · 4 commands · 2 agents
Optimize software performance through user-journey baselines, profiling, representative benchmarks, controlled experiments, and field verification. Use when asked to make an application, service, workflow, or hot path faster or more efficient, or to build the measurement loop first. Do not use for a reliability incident, capacity forecast, generic product A/B test, or operating a named telemetry or load-testing tool without an optimization objective.
194 skills
Design & research — coming soon
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.