oat-project-capture

Create an OAT project from a git branch and conversation history.

1|Updated Jan 26, 2026

Search Tags:#git #project management #workflow automation #artifact generation #code capture #retroactive tracking

Ready to run

npx skills add https://github.com/tkstang/open-agent-toolkit --skill oat-project-capture

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: oat-project-capture
Source: https://github.com/tkstang/open-agent-toolkit/tree/main/.agents/skills/oat-project-capture
Command: npx skills add https://github.com/tkstang/open-agent-toolkit --skill oat-project-capture

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill allows you to retroactively create a structured OAT project from work that was completed outside the standard OAT workflow, ensuring all your efforts are tracked and documented.

Core Features & Use Cases

Retroactive Project Creation: Turn existing branches and conversation history into a formal OAT project.
Artifact Population: Automatically generates discovery.md from conversation context and implementation.md from commit history.
Use Case: You made a quick fix on a feature branch without starting an OAT project. Now, you want to formalize that work, add it to your project tracking, and prepare it for a PR. This skill will create the project structure and populate the necessary files.

Quick Start

Use the oat-project-capture skill to create a project from the current branch and conversation history.

Frequently Asked Questions about oat-project-capture

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I retroactively track untracked git branch work into a project?▼

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.

Can I generate project artifacts from existing git commit history?▼

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.

Do I need the OAT CLI installed to capture untracked work?▼

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.

What's the best way to formalize a quick fix into a tracked project for a PR?▼

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.

When should I use retroactive tracking for project management?▼

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.

How does conversation context populate project discovery files?▼

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.