oat-project-capture

To retroactively track git branch work, this skill extracts conversation context and commit history to populate `discovery.md` and `implementation.md`, transforming untracked branch changes into a formal, documented OAT project ready for review.

Yes, you can generate project artifacts from git commit history. The skill analyzes branch commits to automatically populate `implementation.md`, capturing technical changes and development progress made outside the standard workflow.

Yes, the OAT CLI is required to capture untracked work. You also need git and access to conversation context to analyze past development actions and generate the structured project files for formal tracking.

The best way to formalize a quick fix is through retroactive project creation. This builds the project structure from the existing branch and conversation history, populating necessary documentation files to prepare the work for a pull request.

Use retroactive tracking when you complete work on a feature branch without starting a formal project. It ensures all development efforts are documented, tracked, and prepared for pull requests after the work is already done.

Conversation context populates project discovery files by analyzing historical dialogue to extract requirements and decisions. It automatically generates a `discovery.md` file that captures the initial problem scope and exploration phase.