project-tracker

Create one markdown file per project with YAML frontmatter for status, category, priority, and dates, plus sections for goal, current state, next action, blockers, and a log. Maintain an index.md that lists one line per project grouped by status so the catalog stays glanceable.

Say "add a project" or "start tracking [thing]" and the Skill runs a short interview covering name, goal, success criteria, category, domain, and next action. It then writes the project file, updates the index, and confirms the new entry.

A project is a semi-complex undertaking spanning more than one work session, such as a migration, feature build, or video series. One-off tasks and daily to-dos belong in the daily note or inbox, not the project catalog.

Yes, it exposes a morning-context operation that outputs a compact, priority-sorted summary of active projects with state, next action, blockers, and deadlines. Other skills like morning-routine consume this to anchor the day's plan on real project momentum.

The project file moves to the archive folder, its index entry is removed from Active, and completed projects appear under a recent-completed section for 14 days. The Skill also prompts to capture learnings as wiki insights or a short post-mortem log entry.

Projects whose updated date is over 14 days old get a stale tag, and anything untouched for 30-plus days is surfaced to the user. Staleness usually signals a dead project, a vague next action, or shifted priorities, but nothing is auto-archived.