PromptWorks/chapan-intake/SKILL.md

name	description
chapan-intake	The recurring interview for the Chapan Hokkaido relocation mission. Use when the user says "chapan check-in", "chapan intake", "chapan interview", /chapan-intake, or when a weekly nudge asks Daniel for a relocation status update. Interviews Daniel, updates D:\Repos\Chapan profile.md and status.md, appends a dated log, and turns his findings into tracked visa/program/lead dossiers.

chapan-intake — the regular interview

Tracker root: D:\Repos\Chapan. Dates = America/Los_Angeles. Mission: relocate Daniel's family to Hokkaido (rural-inclusive). This skill is how the mission stays current — interview Daniel, then write what you learn into the tracker.

Step 1 — Load context (read first)

Read profile.md (note every TBD and the "Open questions for next interview" list), status.md (blockers, next actions), and leads/README.md. This tells you what's missing and what to follow up on.

Step 2 — Interview (conversational, batched)

Ask in small batches of 3–6 questions, not all at once. Priority order:

1. Fill profile gaps — pursue TBD fields, hardest-gating first: citizenship(s), current residence, spouse/children (ages, schooling), employer & Japan-transfer/remote feasibility, savings/income range, degrees & years experience, Japanese level, rural tolerance, target timeline, hard constraints.
2. New findings — "Since last time, did you find any towns, programs, visa info, listings, or contacts?" Capture specifics (names, URLs, amounts, deadlines, who he talked to).
3. Status changes — blockers cleared/added, timeline shifts, decisions made, scouting trips.

Mechanics:

• Use m_ask_user only for genuinely discrete choices (2–5 options), e.g. "rural / semi-rural / regional city?". Put context in the message before the call.
• Use plain chat questions for free-text answers (names, numbers, places, URLs).
• Don't interrogate — keep it natural and acknowledge answers. Skip questions already answered in profile.

Step 3 — Write back

• profile.md: replace TBD with captured values; bump updated:; set status: incomplete|usable|complete. Refresh the "Open questions for next interview" list at the bottom.
• status.md: update next actions, blockers, key dates, and append a dated line to the decision log when a decision was made. Bump updated:.
• log/YYYY-MM-DD.md (kind: interview): record updates captured, findings + where filed, open questions carried forward. If the file exists for today, append a ## Re-run HH:MM section.

Step 4 — File findings as dossiers

For each concrete finding, create/append the right file with frontmatter + a source URL and retrieved: date:

• a place → leads/Hokkaido/<City>.md (type: chapan-lead, status: new)
• a program → programs/<slug>.md (type: chapan-program)
• visa info → visa/<slug>.md (type: chapan-visa) Then offer to run the matching deep-dive now (chapan-leads, chapan-programs, or chapan-visa) for anything that needs real research, and add it to status.md next actions.

Step 5 — Close

Give a 3–5 line recap: what got updated, what was filed, and the top 1–2 next actions. Suggest when the next check-in should be.

Rules

• Private family data — never share externally without explicit confirmation; keep it in the vault.
• Never fabricate answers; if Daniel doesn't know, leave TBD and keep the open question.