dk-breadcrumb-creator
Traces a workflow end-to-end through the harness-kit monorepo and creates a breadcrumb analysis doc in docs/breadcrumb_analysis/. Use this skill whenever the user wants to document a flow, trace a workflow, understand how a feature works across layers (frontend → backend → worker → CLI), or create debugging guides for a specific flow. Also use when the user mentions 'breadcrumb', 'trace this flow', 'how does X work end to end', 'document this workflow', or /dk-breadcrumb-creator.
npx skills add majiayu000/claude-skill-registry --skill dk-breadcrumb-creator --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# /dk-breadcrumb-creator — Workflow Breadcrumb Analysis Traces a workflow through the harness-kit monorepo and produces a compact debugging reference. The output is for devs and agents who need to find where things break — not for onboarding docs or architecture overviews. ## Context <flow_context> $ARGUMENTS </flow_context> If the context above is empty, ask: "Which flow do you want to trace? Describe it in terms of the user action or system event that kicks it off." ## Step 0: Check existing breadcrumbs Before scoping anything, read `docs/breadcrumb_analysis/_INDEX.md` to see what already exists. This file lists every breadcrumb folder and what it traces. Compare the user's request against the existing entries and make one of three decisions: 1. **Already covered** — The flow is substantially documented in an existing breadcrumb. Tell the user which one covers it and what it contains. Ask if they want to update/extend that existing doc instead of creating a new one. 2. **Partially overlapping** — An existing breadcrumb covers part of the flow (e.g., user asks about "task execution" and `spec-task-lifecycle/02-execute-and-dispatch/` covers the dispatch side but not the harness exe
- Context
- Step 0: Check existing breadcrumbs
- Step 1: Scope the flow
- Step 2: Trace the flow
- Tracing tips
- Step 3: Create the breadcrumb docs
- File 1: FLOW.md — High-level flow
- File 2: DETAILS.md — Detailed trace
- File 3: DEBUG.md — Debugging guide
- Quick commands section guidance
- Step 4: Verify completeness
- Step 5: Output summary
- Style rules
- When to split into sub-flows
Check if a task exists and its current state python taskit/taskit-backend/testing_tools/task_inspect.py <task_id> --brief Tail the backend log filtered to a specific task grep "task_id" taskit/taskit-backend/logs/taskit_detail.log | tail -20 Check celery worker status celery -A config inspect active Check what odin logged for a spec run cat .odin/logs/run_<id>.jsonl | python -m json.tool
What does the dk-breadcrumb-creator skill do?
Traces a workflow end-to-end through the harness-kit monorepo and creates a breadcrumb analysis doc in docs/breadcrumb_analysis/. Use this skill whenever the user wants to document a flow, trace a workflow, understand how a feature works across layers (frontend → backend → worker → CLI), or create debugging guides for a specific flow. Also use when the user mentions 'breadcrumb', 'trace this flow', 'how does X work end to end', 'document this workflow', or /dk-breadcrumb-creator.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill dk-breadcrumb-creator --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.