dev-workflow

Automate the development lifecycle from GitHub issue specification to pull request.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/ryan-mahoney/ryan-llm-skills --skill dev-workflow-ryan-mahoney
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-workflow
Source: https://github.com/ryan-mahoney/ryan-llm-skills/tree/main/skills/dev-workflow
Command: npx skills add https://github.com/ryan-mahoney/ryan-llm-skills --skill dev-workflow-ryan-mahoney

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end development lifecycle from issue specification to PR, reducing manual handoffs and ensuring consistency across phases.

Core Features & Use Cases

  • Orchestrates spec creation, review, branching, implementation, and PR submission across GitHub issues.
  • Manages phase boundaries, worktrees, and environment hooks to enable safe multi-session workflows.
  • Useful for teams that want a repeatable, auditable automation from spec to merge request.

Quick Start

Ask me to run the full dev workflow for an issue number to coordinate spec, branch, implement, and PR.

Frequently Asked Questions about dev-workflow

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

FAQPage Schema
How do I automate the full development workflow from a GitHub issue to a PR?

Automating the GitHub issue to PR workflow involves orchestrating spec creation, review, branching, implementation, and PR submission. This Skill coordinates these phases with worktree handling and continuation hooks to ensure reliable, multi-session delivery.

What is the best way to orchestrate code review and branching across multiple development sessions?

Orchestrating multi-session development requires clear phase boundaries and worktree handling. This Skill enforces a unified flow from specification to code review, managing environment hooks so collaborative delivery remains repeatable and auditable.

Can I use this workflow automation to manage phase boundaries and worktrees for GitHub branches?

Yes, you can manage GitHub branch phase boundaries and worktrees using this automation. It applies a multi-phase orchestration process that handles environment hooks, ensuring safe transitions between specification, implementation, and PR submission.

Does this GitHub workflow automation require any external dependencies to run?

No external dependencies are required to run this GitHub workflow automation. It operates independently to orchestrate the end-to-end development lifecycle from issue specification through branch creation to PR submission.

When do I need orchestration for end-to-end development lifecycle automation?

You need end-to-end development lifecycle orchestration when you want a repeatable, auditable flow from issue specification to merge request. It is useful for reducing manual handoffs and ensuring consistency across spec writing, branching, and implementation phases.

Why does my development workflow break when transitioning between specification and implementation phases?

Development workflows break during phase transitions due to mismanaged handoffs and lack of clear boundaries. This Skill enforces multi-phase orchestration with continuation hooks, ensuring reliable transitions from spec review to branch implementation and PR submission.