New Coffee Research Skill

Capture research synthesis: As you research, note the flavor implications of this coffee's origin, variety, processing, and altitude. These insights get saved to the README's "What to Expect" section — not just presented in conversation.

See: references/RESEARCH_CHECKLIST.md for detailed research patterns.

3. CONSULT Grind Map

Read grind-map.md and find similar coffees:

• Match by: roast level > processing method > origin
• Consider profile style compatibility: A grind setting from a bloom profile at 7.5 bar won't translate directly to a turbo at 6 bar. When presenting matches, include the Profile, Ratio, and Temp columns so the user sees the full extraction context.
• If match found: use as starting point, adjust for freshness and profile style differences
• If no match: use defaults from knowledge/grinders/SETTE_270.md

Freshness adjustment: Fresher beans (fewer days off roast) need coarser grind — CO2 adds puck resistance. If historical match was at 14 days and new bag is 7 days, suggest 1-2 micro steps coarser.

4. SYNTHESIZE Recommendations

Build recommendations using:

• Temperature: From knowledge/ESPRESSO_BREWING_BASICS.md roast guidelines
• Grind: From grind-map match or SETTE_270.md defaults
• Ratio: From processing method patterns (see below)
• Pressure: From knowledge/PRESSURE_GUIDE.md roast × processing matrix (see below)
• Profile: From knowledge/PROFILE_LIBRARY.md by roast/process, adjusted for correct pressure
• Dose: From user-setup.md basket size. Dose = basket size (e.g., 22g basket → 22g dose). Don't underdose.
• Volumetric target: When using a library profile, confirm its volumetric stop matches dose × ratio. Library profiles are sized for 22g.

4b. SELF-CHECK via Multi-Agent Review

Before confirming with the user, run a two-stage reasoning check. Full protocol (claims format, prompt templates, confidence calibration) in references/SELF_CHECK.md.

Step 1 — Extract claims block: From your synthesis, extract a <claims> block listing: GRIND_ESTIMATE (setting + source), GRIND_MATCH_SIMILARITY, GRIND_CONFIDENCE, TEMP, PRESSURE, PROFILE, RATIO, one CONDITIONAL_RECOMMENDATION line per "if X → Y" in the draft, ADJUSTMENT_COUNT.

Step 2 — Spawn Sonnet critic: Spawn a critic via the Task tool (subagent_type: general-purpose) using the Critic Prompt Template from references/SELF_CHECK.md, with your draft and claims block substituted in.

Step 3 — Evaluate result:

• STATUS: CLEAR → proceed to "CONFIRM with User" using your draft
• STATUS: OBJECTIONS → proceed to Step 4

Step 4 — Spawn Opus arbiter (only when objections found): Spawn via Task tool (subagent_type: general-purpose, model: opus) using the Arbiter Prompt Template from references/SELF_CHECK.md. Use the arbiter's corrected output when confirming with the user.

The grind confidence note from references/SELF_CHECK.md is always included in the Starting Parameters table — even when the critic returns CLEAR.

5. CONFIRM with User

Before finalizing, ask:

"This [process] [origin] typically shines with [approach]. Would you like to start there, or prefer a more conservative/adventurous approach?"

Options to offer:

• Conservative: Classic profile, standard ratio (pressure matched to processing method — not always 9 bar)
• Recommended: Profile matched to bean characteristics (roast, process, intensity)
• Adventurous: Bloom profile or turbo shot if appropriate

6. UPLOAD Profile (if requested)

Use MCP tool to upload:

manage_profile(action="create", profile_name="[Coffee Name] [AI]", temperature=X, phases=[...])

Always add [AI] suffix to profile names.

7. SAVE to Repository

Create a coffee directory and save the research:

1. Create directory: coffees/{roaster}-{coffee-name}/ (kebab-case, e.g., coffees/perc-ethiopia-chelchele/)
2. Write README.md using this template:

# {Roaster} {Coffee Name}

## Bean Profile

| Field | Value |
|-------|-------|
| **Roaster** | ... |
| **Origin** | ... |
| **Process** | ... |
| **Roast Level** | ... |
| **Variety** | ... |
| **Altitude** | ... |
| **Tasting Notes** | {roaster's published tasting notes — actual descriptors, not a placeholder} |
| **Roast Date** | ... |

## What to Expect

{2-3 sentence summary of the coffee's character and what makes it interesting for espresso.
Synthesize origin, variety, processing, and altitude into flavor expectations.}

- **Origin character:** {What this origin typically brings — fruit profile, acidity, body}
- **Variety ({name}):** {How this variety behaves — density, flavor tendencies, quirks}
- **Processing ({method}):** {How processing affects flavor and why we chose this profile style}
- **Density/Altitude:** {If notable (1800+ masl), mention implications for grind and temp}

{Include only bullets that add genuine insight — omit any that just repeat the Bean Profile
table. 2-4 bullets is typical.}

## Profiles

| Profile | Style | Temp | Pressure | Ratio | File |
|---------|-------|------|----------|-------|------|

## Tasting Notes

3. If a profile was uploaded, also save the JSON to the same directory and fill in the Profiles table row
4. Remove .gitkeep from coffees/ if it exists (no longer needed once real content is present)
5. No confirmation needed—this is a standard workflow step

8. Set Active Coffee

Update the Active Coffee section in user-setup.md with:

• Coffee: Full coffee name (e.g., "PERC Ethiopia Chelchele")
• Directory: Path to the coffee directory (e.g., coffees/perc-ethiopia-chelchele)
• Roast Date: From bag info, or "—" if unknown

No confirmation needed—standard workflow step.

9. Private Repo Commit

1. Read .data-repo-path at the project root.
   • If absent: skip silently (user has no private repo — this is expected for new setups).
   • If present: proceed.
2. Run as separate Bash calls (no chaining, no git -C), substituting {private_repo} with the path from .data-repo-path:
   • git --git-dir={private_repo}/.git --work-tree={private_repo} add -A
   • git --git-dir={private_repo}/.git --work-tree={private_repo} commit -m "new-coffee: add {coffee-name}"
   • git --git-dir={private_repo}/.git --work-tree={private_repo} push
3. If push fails: inform the user — "Private repo push failed — changes saved locally. Run git push manually in {private_repo_path} when credentials are available."

Output Format

## Coffee Research: [Name]

### Bean Profile
- **Roaster:** [roaster]
- **Origin:** [country, region]
- **Process:** [washed/natural/honey/anaerobic]
- **Roast Level:** [light/medium/dark]
- **Variety:** [if known]
- **Tasting Notes:** [from roaster]
- **Days Off Roast:** [X days, or "unknown"]

### Similar Coffees in Your History
[Table from grind-map.md matches, or "No similar coffees yet"]

### Recommended Starting Parameters
| Parameter | Value | Reasoning |
|-----------|-------|-----------|
| Temperature | X°C | [roast level rationale] |
| Grind | XY | [from history or default, freshness adjusted] |
| Ratio | 1:X | [process rationale] |
| Profile | [name] | [why this profile] |
| Dose | Xg in → Xg out | [basket size rationale] |

### Profile
[Link to PROFILE_LIBRARY.md profile, or custom JSON if creating new]

### Saved To
`coffees/{roaster}-{coffee-name}/README.md`
Set as active coffee in `user-setup.md`

### What to Watch For
- [Specific guidance for first shot based on bean characteristics]
- [What taste outcomes to expect]
- [When to adjust and in which direction]

Note: "What to Watch For" above is conversational guidance for the user's first shot. Research synthesis (origin, variety, processing insights) is separately saved to the README's "What to Expect" section in Step 7.

Quick Reference

User says: "I got a new bag of [coffee]" Action: Extract info → research → consult grind map → recommend → confirm → set active

User shares photo: Action: Vision extract → research → consult grind map → recommend → confirm → set active

User says: "/new-coffee" Action: Ask what coffee they have, then proceed with workflow → set active