add-blockerlisted

# /ogre:add-blocker Use this skill when the user wants to add a blocker to an issue Ogre is already tracking, discovered after `/ogre:feature` ran (not just at feature-creation time via `--blocks`). ## Inputs - The target issue number (required, must already have Ogre state). - The blocker itself, same input types as `/ogre:feature` — one of: - GitHub issue number (GitHub-only, resolved via `gh` + the project's git remote) - Full issue/page URL — GitHub, GitLab, self-hosted GitLab, Bitbucket, Jira, or any other tracker. Non-GitHub links are fetched generically as page text (no API client), not via `gh`. - Local file path — `.md`/`.txt` copied verbatim, `.docx` text-extracted - Freeform statement via `--statement "..."` (no issue/URL/file needed) - Optional `--name blocker-slug` (only used with `--statement`). - Optional `--remarks "..."` — a freeform note on this blocker's status (e.g. `"PR merged"`, `"under review"`, `"blocking, not started"`). It's tied to this specific blocker and travels with it into planning. Omit it and the blocker is stored plain, with no remark. If the user mentions a status when adding the blocker, capture it here. - Optional `--planner claude|codex`, `--model MODEL`, `--reasoning LEVEL` — defaults to whichever planner `/ogre:feature` already seeded for this issue if omitted. - `--main` — revise the plan inline in this session instead of spawning an isolated subprocess (loses context isolation; only pass when the user explicitly wants that