oat-project-next

Read OAT project state and dispatch to the next lifecycle skill.

Updated May 9, 2020
One-click install
npx skills add https://github.com/tkstang/sequence --skill oat-project-next
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: oat-project-next
Source: https://github.com/tkstang/sequence/tree/main/.agents/skills/oat-project-next
Command: npx skills add https://github.com/tkstang/sequence --skill oat-project-next

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the reading of project state in OAT workflows and determines the next lifecycle action to invoke the appropriate skill automatically.

Core Features & Use Cases

  • Project State Reading: Reads project state from specified files and frontmatter.
  • Lifecycle Routing: Dispatches to the correct next skill based on project phase and status.
  • HiLL Gate Management: Routes to current phase for approval if HiLL gate is pending.
  • Review Safety Check: Checks for unprocessed reviews before dispatching to the target skill.
  • Post-Implementation Router: Handles tasks after the implementation phase, including revision tasks, unprocessed reviews, final code review, summary generation, and PR creation.

Quick Start

Invoke the 'oat-project-next' skill to read project state and determine the next action for the active OAT project.

Frequently Asked Questions about oat-project-next

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

FAQPage Schema
How do I automate project state reading and routing in OAT workflows?

Automating project state reading in OAT workflows requires a skill that reads project state from specified files and frontmatter, then dispatches to the correct next lifecycle skill based on project phase and status.

How does lifecycle dispatch handle pending HiLL gates in project management?

Lifecycle dispatch handles pending HiLL gates by automatically routing the project to its current phase for approval, ensuring that HiLL gate requirements are met before proceeding to the next workflow skill.

Can I use scripts and references to manage post-implementation tasks like PR creation and code review?

Yes, you can use scripts and references to manage post-implementation tasks, as the router handles revision tasks, unprocessed reviews, final code review, summary generation, and PR creation automatically.

What files do I need to prepare before automating project lifecycle routing?

Automating project lifecycle routing requires state.md and artifact files for analysis, as the skill reads these project files to determine the current phase and perform review safety checks.

Why does lifecycle automation check for unprocessed reviews before dispatching to the target skill?

Lifecycle automation checks for unprocessed reviews before dispatching to the target skill to ensure review safety, preventing the workflow from advancing when pending reviews still require attention.

Does oat-project-next work without external dependencies for workflow automation?

Yes, oat-project-next operates without external dependencies, using its own scripts and references to read project state and determine the next action for the active OAT project.