dev-cycle

Automate implementation workflows by selecting high-RICE actions and creating Draft PRs.

5|1|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/mataeil/OODA-loop --skill dev-cycle-mataeil
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-cycle
Source: https://github.com/mataeil/OODA-loop/tree/main/skills/dev-cycle
Command: npx skills add https://github.com/mataeil/OODA-loop --skill dev-cycle-mataeil

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the end-to-end implementation workflow by selecting the highest-RICE action from the queue and delivering it through a dedicated branch and a Draft PR, reducing manual overhead and ensuring auditable changes.

Core Features & Use Cases

  • Selects the top-priority action from agent/state/evolve/action_queue.json by RICE score and transitions it to in_progress, with safeguards and memos.
  • Creates a dedicated auto/dev-cycle branch, applies changes in a controlled sequence, and drafts a PR for human review without auto-merging.
  • Records progress back into action_queue.json and generates a structured PR body with notes on partial completion or safety restrictions.

Quick Start

Invoke the dev-cycle workflow on a project with pending actions to automatically create a branch and a Draft PR.

Frequently Asked Questions about dev-cycle

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

FAQPage Schema
How do I automate end-to-end implementation pipelines from a prioritized action queue?

Automated implementation pipelines select the highest-RICE action from your queue, apply changes to a dedicated branch, and deliver a Draft PR for human review. This workflow enforces safety policies, runs tests, and records status updates for full traceability.

Can I automatically create a branch and draft pull request without auto-merging?

Yes, automated workflows create a dedicated branch, apply changes in a controlled sequence, and draft a pull request without auto-merging. This ensures all automated changes remain paused for human review before integration into the main codebase.

How does continuous delivery handle partial pull requests when changes exceed size limits?

Continuous delivery workflows manage size limits by generating partial pull requests. When changes exceed size thresholds, the automation drafts a PR with structured notes detailing the partial completion status and any safety restrictions encountered.

What happens when automation cannot proceed during code review and continuous delivery?

When automation cannot proceed, the workflow supports optional manual intervention. It enforces safety policies, halts the automated sequence, and generates a structured PR body with meta notes explaining the exact blockage.

Does automated branching require a specific action queue format to prioritize tasks?

Automated branching requires an action queue, such as action_queue.json, where tasks are scored by RICE. The workflow reads this file, transitions the top-priority item to in_progress, and records progress back into the queue for traceability.

Is manual intervention required for safety checks in automated pull request workflows?

Manual intervention is optional for safety checks in automated pull request workflows. The automation enforces safety policies independently, but pauses for human input when it cannot proceed, documenting the restriction in the PR body.