State files

Everything the coach knows about you lives in skillplug-state/, as plain Markdown and CSV you can read and edit.

skillplug-state/
skillplug-state/├── README.md├── shared/                  shared by every SkillPlug pack│   ├── profile.md           who you are│   ├── timeline.md          month-by-month map across packs│   └── deadlines.md         every dated deadline, sorted├── step1/                   one folder per pack (step2/, aways/, planner/)│   ├── state.md             the coach's current view│   ├── session-log.md       append-only session journal│   ├── tasks.md│   ├── decisions.md│   ├── scores.csv│   ├── weak-areas.md│   ├── daily-log.csv│   ├── miss-log.csv│   ├── reviews/             YYYY-Www.md weekly reviews│   ├── artifacts/           schedules, debriefs, trackers│   ├── archive/│   └── handoff.md           written for the next pack├── print/                   printable HTML and PDF files└── dashboard/index.html     the local dashboard

Folders are created on first use. If shared/ already exists from another pack, it is reused.

state.md

The agent-managed fields the coach overwrites each session:

step1/state.md
<!-- agent-managed -->pack: step1-packpack_version: 2.1status: active | paused | completecurrent_phase: 0N-folder-namecurrent_subskill: s1-...last_session: YYYY-MM-DDnext_weekly_review: YYYY-MM-DDweekly_review_day: Sundaynext_actions:  1. YYYY-MM-DD: ...  2. YYYY-MM-DD: ...  3. YYYY-MM-DD: ...streak_days: 0account_sync: unsetlast_account_sync:notes: one line on anything the next session must know

account_sync is unset, on, off, or paused. See Your dashboards. Your SkillPlug key is never stored here.

Shared files

FileFormat
profile.mdSections: identity, program, exams, specialty interests, capacity, constraints, accommodations (status only), resources, what has worked, state_location. The coach asks before every write.
deadlines.mdA table: date, item, pack, source/URL, status, notes. Status is todo, done, missed, or moved.
timeline.mdA month-by-month map with a "today" marker.

Board pack files

scores.csv

step1/scores.csv
date,source,form,mode,n_questions,percent_correct,equated_percent_correct,pass_probability,low_pass_overlap,notes

Step 2 CK uses date,source,form,mode,n_questions,percent_correct,estimated_score,pass_probability,notes. Old rows are never edited; corrections are new rows.

daily-log.csv

daily-log.csv
date,planned_items,planned_questions,hours,questions_done,percent_correct,review_done,anki_done,sleep_hours,energy_1to5,minimum_met,note

miss-log.csv

step1/miss-log.csv
date,source,system,discipline,miss_type,concept,takeaway,retest_date

Step 2 CK orders discipline before system.

Markdown files

FileFormat
weak-areas.mdrank, area, evidence, action, re-test date, status (open, improving, resolved, parked)
tasks.md- [ ] task (due YYYY-MM-DD) [phase], ticked as - [x] ... (done YYYY-MM-DD)
decisions.mddate, decision, options considered, why, revisit if
session-log.mdOne dated entry per session: what you did, numbers, decisions, next action

Away Rotations files

aways/away-tracker.csv
program,specialty,elective_code,city,via,open_date,submit_by,host_fee,requirements,documents_status,dates_requested,status,offer_date,response_deadline,dates_accepted,housing,est_cost,letter_possible,fit_score,source_checked,notes
aways/letters.csv
writer,role,rotation_or_context,letter_type,specialty,status,asked_date,due_date,uploaded_date,last_contact,thank_you_sent,notes

aways/scores.csv is date,source,result,notes.

Editing by hand

You can edit any file. Keep CSV headers as they are, use YYYY-MM-DD dates, and edit outside the <!-- agent-managed --> sections in Markdown files. If something looks wrong, say "my state looks broken" and the coach runs repair mode: it lists inconsistencies, proposes fixes, and asks before writing.

Never stored

Passwords, logins, USMLE, NBME, or AAMC IDs, Social Security numbers, financial account numbers, or patient-identifying details. If you paste any of these, the coach doesn't save them and tells you why.

Previous
Pack structure