researchprior-artlisted

Research prior art for: $ARGUMENTS ## Process ### Search Identify relevant sources based on context: - **GitHub**: Search for repositories matching the problem space - **Package registries**: npm, PyPI, crates.io, pkg.go.dev—infer from current project or query - **Web search**: For broader landscape understanding Run searches in parallel. Infer the ecosystem from: 1. Current project's language/framework (if present) 2. Query terms (e.g., "React hook for X" implies npm) 3. Ask only if genuinely ambiguous ### Investigation Start with 2-3 most promising projects: 1. Read README and high-level docs to assess relevance 2. Examine code only when relevance is confirmed AND implementation details matter 3. Dispatch parallel `Agent` calls per project, with explicit focus areas If results don't satisfy the query, expand to more projects. **Agent dispatch example:** ``` Investigate [project] for prior art on [topic]: - How does it approach [specific aspect]? - What tradeoffs does it make? - What can we learn for our use case? ``` ### Synthesis Gather findings and produce a recommendation: - Identify common patterns across solutions - Note meaningful variations in approach - Infer intent: - "build X" → learn patterns, inform implementation - "library for X" → find dependencies to use directly ## Output Format Respond in the conversation with structured markdown, not files: ```markdown ## Prior Art: [Topic] ### Summary [Common patterns, key variations, recommendation bas