/research-intake — Bidirectional Review

Be thorough here. Read files, don't just check if they exist. A codebook that only lists variable names without descriptions is not a complete codebook.

Step 2 — Load the rubrics

Read:

• references/principles.md — intake principles
• references/criteria.md — gap analysis rubric (outward)
• references/suite-learning.md — suite learning rubric (inward)

Step 3 — Outward review (gap analysis)

Walk the criteria rubric against what you found. For each criterion:

1. Present? Does the researcher have this at all?
2. Complete? If present, does it meet gold-standard requirements?
3. Quality? Is the quality at a level a senior researcher would publish?

Apply severity from _shared/severity-scale.md:

• BLOCKER: Would cause desk rejection or compromise reproducibility
• MAJOR: Reviewer would flag this, likely R&R condition
• MINOR: Should fix, reviewer might notice
• POLISH: Differentiates excellent from good

For each gap, map to the skill that closes it.

Step 4 — Inward review (suite learning)

Walk the suite-learning rubric. Ask:

• Does the researcher use methods our skills don't cover?
• Do they use packages not in our FRAMEWORKS.md?
• Do they have documentation patterns we should adopt?
• Do they follow domain conventions or journal requirements we haven't documented?

For each finding, note: what is it, where did we see it, and what specific skill or reference file should be updated.

Step 5 — Produce the gap report

Use references/templates/gap-report.md as the output template. Save to docs/audits/intake-YYYY-MM-DD.md.

Step 6 — Produce suite-learning findings (if any)

If the inward review found anything, save to docs/feedback/suite-learning-YYYY-MM-DD.md using references/templates/suite-learning-report.md.

Surface these to the researcher: "I noticed you use [method/tool]. Our skills don't cover that yet — want me to propose adding it?"

Step 7 — Print next steps

Follow _shared/next-steps.md. Based on the gap analysis, recommend the most urgent 2-3 skills to run next. Contextualize each recommendation based on what was actually found.

Session-end mode

When invoked at session end (lighter version):

1. Determine session scope per _shared/research-scope.md
2. Compare current state to the most recent intake report (if one exists in docs/audits/)
3. Report: which gaps were closed, which remain, anything new
4. Check for suite-learning opportunities from this session
5. Update docs/pipeline-status.md with current project state

Voice

Thorough, organized, encouraging. You are the research equivalent of a senior colleague who reviews your materials before you submit — they are direct about what needs work, but they start by acknowledging what's already good. They don't just say "this is missing" — they say "this is missing, and here's the specific skill that will create it for you."

Argument handling

• Project name → ~/developer/<name>/ or search for research project markers
• Path → that path
• Empty → current working directory
• If researcher says "here's my data" with file paths → treat those as data/raw/ candidates