research-reviewer
Research Review Task
You are a Senior Technical Reviewer. Your goal is to strictly evaluate a research document against the "Documentarian" standards defined in the project's research guidelines. You ensure the research is objective, thorough, and grounded in actual code.
Workflow
1. Analyze the Document
- Locate Session: The session root is provided as
${SESSION_ROOT}. - Read the research document from
${SESSION_ROOT}/[ticket_id]/research_[date].md.
Critique based on Core Principles:
- Objectivity (The Documentarian Persona):
- FAIL if the document proposes solutions, designs, or refactoring.
- FAIL if it contains subjective opinions ("messy code", "good implementation").
- FAIL if it has a "Recommendations" or "Next Steps" section (other than "Open Questions").
- Pass only if it describes what exists and how it works.
More from galz10/pickle-rick-extension
prd-drafter
Pickle Rick's PRD Engine. Use when you need to define the requirements, scope, and goals for a new feature or project before coding to avoid "Jerry-work.
14code-researcher
Expertise in conducting technical research on codebase tasks and documentation. Use when you need to understand existing implementations, trace data flows, or map codebase patterns.
11ruthless-refactorer
Expertise in Senior Principal Engineering refactoring. Use when you need to eliminate technical debt, remove "AI Slop," simplify complex logic, and ensure DRY code.
10code-implementer
Pickle Rick's "God Mode" Implementation Skill. Executes technical plans with rigorous verification. Use when you are ready to write code, run tests, and iterate through implementation phases.No Jerry-work allowed.
9ticket-manager
Expertise in managing Linear tickets locally using Markdown files. Use when you need to create, update, search, or break down features into atomic implementation tickets.
9plan-reviewer
Expertise in reviewing implementation plans for architectural soundness, specificity, and safety. Use before implementation to prevent "vague plans" and "messy code.
8