oat-project-review-receive

Convert review findings into plan tasks and update project documentation.

1|Updated Jan 26, 2026
One-click install
npx skills add https://github.com/tkstang/open-agent-toolkit --skill oat-project-review-receive
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: oat-project-review-receive
Source: https://github.com/tkstang/open-agent-toolkit/tree/main/.agents/skills/oat-project-review-receive
Command: npx skills add https://github.com/tkstang/open-agent-toolkit --skill oat-project-review-receive

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of incorporating feedback from code reviews into actionable development tasks, ensuring that identified issues are systematically addressed and closed.

Core Features & Use Cases

  • Automated Task Creation: Converts findings from review artifacts into specific, actionable tasks within the project plan.
  • Status Tracking: Updates project documentation (plan.md, implementation.md) to reflect the review status and next steps.
  • Artifact Archiving: Safely archives processed review documents for historical reference.
  • Use Case: After a code review identifies several critical bugs and minor stylistic issues, this Skill automatically creates new tasks in plan.md for the bugs, updates implementation.md with a summary, and archives the review document.

Quick Start

Use the oat-project-review-receive skill to process the latest review findings for the active project.

Frequently Asked Questions about oat-project-review-receive

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

FAQPage Schema
How do I convert code review findings into actionable tasks?

You can automate task creation from review artifacts by converting findings directly into actionable plan tasks. This updates project documentation like plan.md and implementation.md while archiving the review document for reference.

How does a feedback loop handle deferrals for minor code review issues?

The feedback loop handles deferrals by explicitly managing review cycles and deferring medium or minor findings. Critical issues are converted into immediate actionable tasks, while less severe findings are scheduled for future resolution.

Can I update project documentation automatically after an issue tracking review?

Yes, project documentation updates automatically after issue tracking reviews by modifying plan.md with new tasks and implementation.md with status summaries. This maintains project state consistency and ensures systematic gap closure.

What is the best way to archive processed review documents?

The best way to archive processed review documents is automatically after task creation. The tool safely stores historical review files for reference once the actionable feedback has been extracted and added to the project plan.

Does this task management approach support both code and artifact review types?

Yes, this task management approach supports both code and artifact review types. It processes findings from either review type to ensure consistent gap closure and project state updates across different review contexts.

Why update implementation.md after processing review findings?

Updating implementation.md after processing review findings provides a summary of the review status and next steps. This maintains project state consistency by documenting which gaps were closed and what actions remain.