block-journeylisted

# Skill: block-journey ## When to Use Run `/block-journey <name>` to document how a block or component works from two perspectives: the editor creating content, and the visitor consuming it. Use when onboarding to an unfamiliar block, before modifying one, or after building one to capture its contracts. Parse `$ARGUMENTS` to extract the block name and an optional path scope: - **`accordion`** — search the entire working directory for a block named "accordion" - **`rte-blocks/accordion`** — search only within directories whose path contains "rte-blocks" for "accordion" - **`mu-plugins/rtm-blocks/faq`** — search only within directories whose path contains "mu-plugins/rtm-blocks" for "faq" If `$ARGUMENTS` contains a `/`, treat everything before the last `/` as a **path substring filter** and everything after as the block name. Match the filter against the full directory path, not just the immediate parent. This matters when the same plugin name exists under different parent directories (e.g., `plugins/rtm-blocks` vs `mu-plugins/rtm-blocks`). If no `/`, treat the entire argument as the block name and search broadly. When the path filter matches multiple locations, list them and ask the user which one to document. If `$ARGUMENTS` is empty, ask the user which block or component to document. Do NOT modify any source files. This is documentation, not implementation. ## Method ### Step 1: Discover Files Search the working directory for all files related to the block name fr