You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
41 lines
2.5 KiB
41 lines
2.5 KiB
2 months ago
|
---
|
||
|
|
name: "chapan"
|
||
|
|
description: "Mission control for the Chapan Hokkaido relocation project. Dashboard, router, and digest over the tracker at D:\\Repos\\Chapan. Use when the user says /chapan, \"chapan\", \"chapan status\", \"chapan dashboard\", \"chapan digest\", or asks how the Japan/Hokkaido relocation is going. Routes to chapan-intake, chapan-visa, chapan-programs, chapan-leads."
|
||
|
|
---
|
||
|
|
|
||
|
|
## chapan — mission control
|
||
|
|
|
||
|
|
Tracker root: `D:\Repos\Chapan`. All dates use America/Los_Angeles (`Get-Date -Format yyyy-MM-dd`).
|
||
|
|
Mission: relocate Daniel's family to **Hokkaido, Japan, including rural areas**.
|
||
|
|
|
||
|
|
This skill is the front door. With no subcommand, run **status (dashboard)**.
|
||
|
|
|
||
|
|
### Subcommands
|
||
|
|
- `/chapan` or `/chapan status` → dashboard
|
||
|
|
- `/chapan digest` → change briefing (optionally saved to log)
|
||
|
|
- natural language ("how's the move going?") → dashboard, then point to the right sub-skill
|
||
|
|
|
||
|
|
### Dashboard (read-only)
|
||
|
|
1. Read `status.md` (phase, next actions, blockers, key dates) and `profile.md` (count remaining `TBD` fields = profile completeness).
|
||
|
|
2. Scan `leads/Hokkaido/*.md`, `visa/*.md`, `programs/*.md` frontmatter (`status:`, `updated:`, `retrieved:`). Skip `README.md` index files.
|
||
|
|
3. Present concisely:
|
||
|
|
- **Phase** + profile completeness (e.g. "7 fields still TBD").
|
||
|
|
- **Leads**: count by status; list `hot`/`investigating` with one-line why.
|
||
|
|
- **Visa**: pathways by status + fit.
|
||
|
|
- **Programs**: by relevance/status.
|
||
|
|
- **Stale flags**: any dossier with `retrieved` >90 days, or `hot`/`investigating` lead `updated` >14 days.
|
||
|
|
- **Next actions** (from status.md) and **last log entry** date.
|
||
|
|
4. End with the single most useful next step and which skill runs it.
|
||
|
|
Do NOT write files in status mode.
|
||
|
|
|
||
|
|
### Digest
|
||
|
|
Compare `updated:` dates across all dossiers + the latest `log/` entries. Summarize what changed since the last digest (default last 7 days, or since the user's stated point), list stale items needing re-verification, and give 3 concrete recommended next actions. Offer to save it to `log/YYYY-MM-DD.md` with `kind: finding`. Used on demand and by the monthly digest automation.
|
||
|
|
|
||
|
|
### Routing
|
||
|
|
If the user's real intent is to be interviewed → `chapan-intake`; research visas → `chapan-visa`; programs → `chapan-programs`; investigate a place → `chapan-leads`. You may just hand off by running that skill's flow.
|
||
|
|
|
||
|
|
### Rules
|
||
|
|
- Parse frontmatter with simple line regex; no YAML libs.
|
||
|
|
- Private family data — never share externally without explicit confirmation.
|
||
|
|
- Be honest about gaps; never fabricate dossier facts.
|