Results for “prior-art”

Search your references and context knowledge base for patterns relevant to a current task. Use before implementing anything non-trivial to surface prior art from your analyzed repos.

Research existing tools, libraries, and patterns before writing custom code by invoking a researcher agent.

Guides a research-before-coding workflow, searching existing tools, libraries, and patterns before writing custom code, with decision matrices and integration with agent workflows.

Guides the agent to research existing tools, libraries, and patterns before writing custom code, using parallel searches across package registries, MCP servers, skills, and GitHub, then evaluating and deciding to adopt, extend, or build.

Evidence-based investigation of issues, bugs, API calls, integrations, and other aspects of software development that need a deep dive to find the root cause and solutions. Use when you need to debug, troubleshoot, diagnose, or figure out why something is broken. Does not review code for quality or style — use code-review for auditing changes or post-code-review-to-pr for posting review feedback to GitHub. Does not assess architectural health or structural risk — use architectural-analysis for architectural concerns. Does not research open-ended options, prior art, or how something works when nothing is broken — use research for that. Does not capture feedback on Han's own skills — use han-feedback for that.