myna-dev-task-protocol

Coordinate commit, review, and fix loops for Myna development tasks.

8|1|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/agentflock/myna --skill myna-dev-task-protocol
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: myna-dev-task-protocol
Source: https://github.com/agentflock/myna/tree/main/.claude/skills/myna-dev-task-protocol
Command: npx skills add https://github.com/agentflock/myna --skill myna-dev-task-protocol

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This protocol provides a structured, automated workflow that coordinates the end-to-end commit, review, and fix loop for Myna development tasks performed by subagents. It ensures changes are prepared, reviewed, and reported back without performing any pushes.

Core Features & Use Cases

  • Automated dev-task quality loop: commit, review, fix, and report back
  • Enforces up to three review rounds and mandatory fixes for Critical and Important issues
  • Not user-invocable; orchestrator-owned pushes and centralized coordination
  • Clear branch and commit hygiene with guided steps for staging and amendments

Quick Start

Trigger the subagent task protocol after implementation to start the three-round review cycle and report back.

Frequently Asked Questions about myna-dev-task-protocol

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

FAQPage Schema
How do I automate a commit, review, and fix loop for subagent development tasks?

A structured dev-task protocol coordinates the end-to-end commit, review, and fix loop for subagent development tasks. It enforces strict branching, staging, and amend commit steps to ensure changes are tracked correctly by the central orchestrator.

How does the automated code review process handle unresolved critical issues?

The automated code review process enforces up to three review rounds to handle unresolved critical issues. It ensures all Critical and Important issues are fixed and resolved before reporting task status back to the orchestrator.

Can I trigger the dev-task review protocol manually for individual commits?

No, the dev-task review protocol is not user-invocable. It is an orchestrator-owned process designed for centralized coordination across subagents, ensuring automated quality loop enforcement without manual intervention or pushes.

What is the best way to ensure branch and commit hygiene during automated subagent workflows?

The best way to ensure branch and commit hygiene is to enforce guided steps for staging and amend commits. This structured workflow ensures all changes are prepared, tracked, and reported correctly without performing git pushes.

Why does my subagent workflow fail to track changes correctly without a centralized review loop?

Subagent workflows fail to track changes without a centralized review loop because they lack strict branching and staging enforcement. An automated dev-task protocol coordinates commit and amend steps centrally to ensure correct tracking.