daily-landingslisted

<!-- # sync-safe --> # Daily Landings ## Overview Landings are **outcomes, not tasks.** "Ship the auth flow PR" not "work on auth." They represent what the user wants to have **achieved** by end of day. ## Persistence - Landings are saved to `landings/YYYY-MM-DD.md` (one file per day, history preserved). - On morning creation: write the full landings file. - On check-in/update: re-read the file, update status on each landing, write back. - The landings file is the source of truth for the day's priorities. ## Weekly Targets Layer Weekly targets are set on Monday mornings. They represent **end-of-week outcomes** that guide daily landing selection throughout the week. ### File Structure - Weekly file: `landings/weekly/YYYY-WXX.md` (ISO week number) - One file per week, persisted for history ### Weekly Targets Format Each weekly target uses `W{n}` prefix: ```markdown ### W1. {outcome} **Status:** Not Started | In Progress | Done | At Risk | Dropped | Stalled | Deprioritized **Daily touchpoints:** Mon, Wed, Fri {narrative about current state} ``` ### Weekly Modes **Mode A: Monday Morning — Set Weekly Targets** Run when no `landings/weekly/YYYY-WXX.md` exists for the current week, or when user says "set weekly landings" / "weekly targets". Procedure: 1. Read `todo.md` — active projects, this week section, waiting-on-others 2. Read `projects/*/context.md` — current state and blockers 3. Read last week's weekly file (if exists) — carry over incomplete targets 4. Present o