critiquelisted

# Critique Command Use this command to get a Distinguished Engineer level technical critique of the current approach and implementation. <!-- recall:begin --> ## Step 0: Prior-art check (MANDATORY) Before critiquing, recall prior learnings from the global knowledge base so we don't re-learn or re-decide something already captured: ```bash uv run "{{HOME_TOOL_DIR}}/skills/recall/scripts/recall.py" \ "<QUERY>" \ --limit 5 --format markdown ``` **Query construction for `/critique`**: a short summary of the approach/code being critiqued + relevant domain keywords (e.g. `"event-sourced migration rollback strategy"`). **What to do with results:** - If a returned learning names a constraint, anti-pattern, or prior decision directly relevant to the task — surface it to the user BEFORE proceeding with this skill's main flow. - If nothing relevant returns — proceed silently, no need to mention the check. - Never block on recall failure. Empty output / non-zero exit is expected when the KB is absent or the subprocess errors — treat it as "no prior art found", not as an error. <!-- recall:end --> ## Usage ``` /critique [type] "context" ``` ## Types - `general` - Overall technical review (default) - `architecture` - System design and patterns review - `performance` - Performance and scalability analysis - `security` - Security implications assessment - `cost` - Total cost of ownership analysis - `complexity` - Overengineering assessment - `all` - Comprehensive review cove