document-work

Decision logging records architectural choices and their consequences using Git history and Markdown templates. It maintains a persistent project memory by documenting tradeoffs, design rationale, and work status, ensuring future developers understand why specific approaches were taken.

Documenting project state involves creating Markdown status updates that track in-progress tasks, blockers, and next steps. By analyzing Git history, this approach maintains an up-to-date log of architectural changes, technology stack evolution, and work progress for team collaboration.

Yes, Git is required to document recurring code structures and API contracts. This Skill analyzes Git commit history to identify patterns, then generates Markdown files using predefined templates to capture API contracts, error handling approaches, and code structures systematically.

You need pattern documentation when completing complex features that introduce new code structures or API contracts. It helps capture recurring approaches and error handling patterns, creating a knowledge base that clarifies implementation details for the next developer.

No, this approach relies on predefined Markdown templates to structure knowledge capture. The templates ensure consistent documentation of work patterns, decisions, and project state by providing a standardized format for memory file generation.