Reframe Feynman for general research workflows

This commit is contained in:
Advait Paliwal
2026-03-20 12:03:35 -07:00
parent 4bb1823a20
commit 806ea80c2c
21 changed files with 242 additions and 9 deletions

View File

@@ -0,0 +1,17 @@
---
description: Compare multiple sources on a topic and produce a source-grounded matrix of agreements, disagreements, and confidence.
---
Compare sources for: $@
Requirements:
- Identify the strongest relevant primary sources first.
- Inspect the top sources directly before comparing them.
- Build a comparison matrix covering:
- source
- key claim
- evidence type
- caveats
- confidence
- Distinguish agreement, disagreement, and uncertainty clearly.
- End with a `Sources` section containing direct URLs for every source used.
- Save the comparison to `outputs/` as markdown if the user wants a durable artifact.

View File

@@ -10,4 +10,5 @@ Requirements:
- Prefer primary sources and note when something appears to be a preprint or secondary summary.
- Separate consensus, disagreements, and open questions.
- When useful, propose concrete next experiments or follow-up reading.
- End with a `Sources` section containing direct URLs for every paper or source used.
- If the user wants an artifact, write the review to disk as markdown.

View File

@@ -9,4 +9,5 @@ Requirements:
- If a public repo exists, inspect it with `alpha_read_code`.
- Compare claimed methods, defaults, metrics, and data handling against the repository.
- Call out missing code, mismatches, ambiguous defaults, and reproduction risks.
- End with a `Sources` section containing paper and repository URLs.
- Save the audit to `outputs/` as markdown.

View File

@@ -16,4 +16,5 @@ Requirements:
- limitations
- conclusion
- If citations are available, include citation placeholders or references clearly enough to convert later.
- Add a `Sources` appendix with direct URLs for all primary references used while drafting.
- Save the draft to `papers/` as markdown.

View File

@@ -9,4 +9,5 @@ Requirements:
- Use `alpha_ask_paper` when a paper's fit is unclear.
- Group papers by role when useful: foundational, strongest recent work, methods, benchmarks, critiques, replication targets.
- For each paper, explain why it is on the list.
- Include direct URLs for each recommended source.
- Save the final reading list to `outputs/` as markdown.

View File

@@ -12,3 +12,4 @@ Requirements:
- If enough information is available locally, implement and run the replication steps.
- Save notes, scripts, and results to disk in a reproducible layout.
- Be explicit about what is verified, what is inferred, and what is still missing.
- End with a `Sources` section containing paper and repository URLs.

11
prompts/research-memo.md Normal file
View File

@@ -0,0 +1,11 @@
---
description: Produce a general research memo grounded in explicit sources and direct links.
---
Write a research memo about: $@
Requirements:
- Start by finding the strongest relevant sources.
- Read or inspect the top sources directly before making strong claims.
- Distinguish facts, interpretations, and open questions.
- End with a `Sources` section containing direct URLs for every source used.
- Save the memo to `outputs/` as markdown if the user wants a durable artifact.