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

@@ -33,6 +33,7 @@ Use this skill when the user wants:
- what remains unresolved
7. If the user wants a durable artifact, write a markdown brief to disk.
8. If you discover an important gotcha about a paper, save it with `alpha_annotate_paper`.
9. End with a `Sources` section that lists direct URLs, not just titles.
## Pitfalls
@@ -50,3 +51,4 @@ Prefer this structure:
- disagreements or caveats
- open questions
- recommended next reading or experiments
- sources

View File

@@ -32,6 +32,7 @@ Use this skill for:
6. Record concrete mismatches, not vibes.
7. Save the audit in `outputs/`.
8. If you find a durable gotcha, save it with `alpha_annotate_paper`.
9. End with a `Sources` section for the paper and repository.
## Pitfalls
@@ -48,3 +49,4 @@ Include:
- mismatches or omissions
- reproducibility risks
- recommended next actions
- sources

View File

@@ -29,6 +29,7 @@ Use this skill for:
4. Use LaTeX only where equations or notation genuinely improve clarity.
5. Keep claims falsifiable and scoped.
6. Save polished drafts to `papers/`.
7. Add a `Sources` appendix with direct URLs to all inspected references.
## Pitfalls

View File

@@ -32,6 +32,7 @@ Use this skill for:
- move to strongest methods
- finish with edges, critiques, or adjacent work
6. Write the final list as a durable markdown artifact in `outputs/`.
7. For every paper, include a direct URL.
## Pitfalls

View File

@@ -0,0 +1,42 @@
---
name: research-memo
description: Use this when the user wants a source-grounded memo, briefing, landscape summary, or background note that is broader than a single paper.
---
# Research Memo
## When To Use
Use this skill for:
- background research
- topic briefings
- market or field overviews
- synthesis across multiple sources
- internal memos that need traceable evidence
## Procedure
1. Find relevant sources first.
2. Inspect the strongest sources directly before synthesizing.
3. Separate:
- established facts
- plausible inferences
- unresolved questions
4. Write a memo with clear sections and a concise narrative.
5. End with a `Sources` section containing direct links.
6. Save the memo to `outputs/` when the user wants a durable artifact.
## Pitfalls
- Do not summarize from search snippets alone.
- Do not omit the source list.
- Do not present inference as fact.
## Deliverable
Include:
- topic
- key findings
- disagreements or caveats
- open questions
- sources

View File

@@ -0,0 +1,44 @@
---
name: source-comparison
description: Use this when the task is to compare multiple papers, reports, or sources and produce a grounded matrix of agreements, disagreements, and confidence.
---
# Source Comparison
## When To Use
Use this skill for:
- comparing papers on the same topic
- reconciling conflicting claims
- assessing multiple sources before making a recommendation
- producing evidence matrices
## Procedure
1. Find and inspect the strongest relevant sources first.
2. For each source, extract:
- main claim
- evidence type
- caveats
- what would falsify or weaken the claim
3. Build a comparison table or matrix.
4. Separate:
- points of agreement
- points of disagreement
- unresolved questions
5. End with a `Sources` section containing direct URLs.
## Pitfalls
- Do not compare sources you have not actually opened.
- Do not blur disagreement into consensus.
- Do not omit source links.
## Deliverable
Include:
- matrix
- agreement summary
- disagreement summary
- confidence assessment
- sources