document-work

To document project decisions and work patterns, this Skill analyzes Git history to automatically generate structured markdown files. It extracts architectural choices, recurring code structures, and ongoing work status to facilitate team knowledge capture.

Capturing architectural decisions is best achieved by logging them into predefined markdown templates. This method records specific architectural choices, tradeoffs, and the underlying development rationale, ensuring valuable project knowledge is retained for future reference.

Yes, you can track work in progress and blockers for session handoffs. The system manages project state by documenting ongoing work status, current blockers, and next steps into structured markdown files, enabling seamless development session transitions.

Yes, this documentation workflow requires Git for version analysis. It relies on Git history to identify significant work, recurring patterns, and project state changes before generating the structured markdown documentation outputs for the team.

You log recurring code structures and API contracts by using pattern capture features. This identifies and documents recurring code structures, API contracts, and error handling approaches into predefined markdown templates for ongoing knowledge retention.