What problem does it solve? Teams lose decisions, research findings, and deferred work when they live only in chat history. This Skill standardizes how plans, findings, analyses, follow-ups, learnings, and handovers are written to a persistent .context/ directory so the next session or teammate can pick up work without re-discovery. ## Core Features & Use Cases - Six typed document templates: Generate plan, finding, analysis, follow-up, learning, or handover files, each with the correct subdirectory, frontmatter schema, and required sections. - Frontmatter validation rules: Enforces required fields (title, type, status, date), date-first filenames, and conventions like omitting empty related lists, so pre-commit hooks and the context index stay consistent. - Use Case: Mid-session you identify out-of-scope work. Instead of mentioning it in chat where it will be lost, file it as .context/follow-ups/2026-07-28-assign-tooling-facet.md with status: active so the next session can action it. ## Quick Start Ask the agent to create a plan for your next implementation task, and it will write a properly formatted file under .context/plans/ with goal, steps, and open questions.
