| name | pmf-wrap |
| description | End-of-day PMF wrap-up. Summarizes the day from today's log, updates the hypotheses it touched (status / signal / evidence — only with explicit confirmation), captures decisions, and appends a dated thesis revision if direction changed. Use at the end of a working day or when the user says 'pmf wrap', 'wrap up my pmf day', 'close out the day', 'update my hypotheses', or types '/pmf-wrap'. |
| argument-hint | [optional: path to the pmf/ tracker root] |
| version | 0.1.0 |
| user_invocable | true |
/pmf-wrap — end-of-day synthesis + hypothesis updates
You are closing out a founder's research day. Your job is to summarize honestly and update the
hypotheses the day actually touched — appending evidence, never overwriting it, and never changing a
claim's status without explicit confirmation.
Before you do anything
- Read
${CLAUDE_PLUGIN_ROOT}/references/honesty-rules.md (NON-NEGOTIABLE), format-spec.md, and evidence-weight.md.
- Resolve the tracker root
$PMF (path arg → git rev-parse --show-toplevel/pmf/ → CWD pmf/).
- Get today's date with
date +%Y-%m-%d.
Steps
1. Load today's log
Read $PMF/log/<today>.md. If it doesn't exist, run a compressed version of the /pmf-start interview
first (ask what happened today), write the log, then continue. Read the hypothesis files listed in its
front-matter hypotheses_touched.
2. Summarize the day into the log
Append to $PMF/log/<today>.md (set/append session: wrap):
## Day summary — a tight, grounded recap built from what's already in the log plus one closing
AskUserQuestion ("Anything to add before I wrap the day?").## Decisions — concrete decisions made today (also mirror them into the front-matter decisions: list). If none, write TBD/none — don't manufacture decisions.
3. Update the hypotheses the day touched
For each id in hypotheses_touched, edit $PMF/hypotheses/H<n>.md:
- Append to
## Evidence and ## Result with a dated bullet (- <date>: …). Never overwrite prior evidence.
- Set
evidence_weight to reflect the real source count: one conversation ⇒ 🔵 and the result text must say n=1; a second independent source ⇒ ⚠️/✅. Add the provenance tag to the sources: list.
- Status / signal changes require explicit confirmation. Use AskUserQuestion: "Move H from
<old> to <new>?" with the allowed values (Open/Testing/Validated/Invalidated; signal —/Mixed/✓). Only change after the user confirms — a status change is a real claim about the venture. Never promote a single quote (n=1) to ✓/Validated.
- Bump the hypothesis
updated: to today.
If the day surfaced a new hypothesis, create $PMF/hypotheses/H<next>.md from ${CLAUDE_PLUGIN_ROOT}/templates/hypothesis.md (next free id), filling only what's grounded; everything else TBD.
4. Thesis + ledger
- If a decision changed direction, append a dated
## Revision — <context> section to $PMF/thesis.md (with confirmation) and bump revisions. Never overwrite the current draft.
- If a new load-bearing claim emerged (something you'll rely on externally), add a row to
$PMF/ledger.md with its Weight, framing/caveat, and Source tag.
5. Confirm and stop
Report exactly which files changed. Suggest /pmf-index to refresh the index, and /pmf-review at the
end of the week. Do not auto-run them.
