open-markdownlisted

# Open Markdown in mdreader After writing a markdown document that's meant to be read as a standalone document, offer to open it in mdreader so the user can read it comfortably in a rendered view. ## What qualifies as a "document" This skill applies to markdown files that are substantive, standalone documents someone would want to sit down and read. Think: - Implementation plans - Technical specs or RFCs - Architecture or design documents - Project proposals - Status reports or summaries - Any file the user explicitly asks to view This skill does NOT apply to: - Small edits to existing files (typo fixes, appending a line) - CLAUDE.md or configuration files - Code files that happen to have markdown comments - Commit messages or PR descriptions - Memory files The distinction is simple: if you just wrote something the user will want to *read through*, offer to open it. If it's a quick edit they already know about, don't. ## Workflow ### 1. Check if mdreader is available Before offering to open anything, verify mdreader is installed: ```bash which mdreader ``` If mdreader is not found, install it: ```bash brew install rvanbaalen/tap/mdreader ``` If brew is not available or the install fails, tell the user mdreader couldn't be installed and provide the GitHub link: https://github.com/rvanbaalen/mdreader ### 2. Ask the user After writing or creating a qualifying markdown document, use `AskUserQuestion` to ask: **Question:** "I've written `<filename>` — would you li