skills.rest
alexgorbatchev
alexgorbatchevCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

agentic-workflow

Coordinate ticket-driven work across isolated branches with implementation and reviewer passes.

1|Updated Apr 17, 2026
Search Tags:#workflow#verification#branching#code-review#ticket-management#lanes
One-click install
npx skills add https://github.com/alexgorbatchev/ai-registry --skill agentic-workflow-alexgorbatchev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agentic-workflow
Source: https://github.com/alexgorbatchev/ai-registry/tree/main/skills/agentic-workflow
Command: npx skills add https://github.com/alexgorbatchev/ai-registry --skill agentic-workflow-alexgorbatchev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinates ticket-driven work across isolated branches/worktrees, enforcing separate implementation and reviewer passes, and mandatory verification before merging to prevent drift and merge risk.

Core Features & Use Cases

  • Isolated work lanes per ticket to avoid cross-contamination between tasks.
  • Separate implementation and reviewer passes with explicit verification steps.
  • Bounded forward-sync to keep primary branch steady while lanes progress.
  • Clear lifecycle for lanes from creation to merged state, with auditable proof.

Quick Start

Create an isolated worklane for a ticket, implement changes there, run verification, and merge back to main once approved.

Frequently Asked Questions about agentic-workflow

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

FAQPage Schema
How do I isolate ticket-driven development work across separate branches?▼

To isolate ticket-driven development, you create a dedicated worklane per ticket, enforce separate implementation and reviewer passes, and require verification before merging to prevent drift and cross-contamination.

What is the best way to enforce branching discipline and verified integration?▼

The best way to enforce branching discipline is by applying bounded forward-sync rules to keep the primary branch steady, while requiring proof-based acceptance and mandatory verification before merging isolated work lanes.

How do I manage a worklane lifecycle from creation to merge?▼

You manage a worklane lifecycle by creating an isolated branch for a ticket, implementing changes there, running formal verification, and merging back to the primary branch once the reviewer pass is approved.

Can I use formal implementation and reviewer passes for multi-stage development tasks?▼

Yes, you can apply formal implementation and reviewer passes to multi-stage development tasks where changes must be isolated, reviewed, verified, and merged one lane at a time to ensure safe, auditable merges.

Why does unverified merging cause drift in isolated ticket branches?▼

Unverified merging causes drift because isolated branches lack bounded forward-sync rules and proof-based acceptance, allowing cross-contamination and merge risk when integrating changes back to the primary branch.

Related Skills

Explore More Software Engineering Skills→
dohernandezdohernandez

workflow-setup

Create per-ticket git worktrees and set up development environments.

Community
Advanced
alangebalangeb

git

Automate git worktree synchronization via rebase and fast-forward merges.

Community
Advanced
smith-hornsmith-horn
75

github-code-review

Coordinate parallel AI agents to review GitHub pull requests and enforce quality gates.

Official
Advanced
HomericIntelligenceHomericIntelligence
18

verify-pr-ready

Validate GitHub Pull Requests for CI status, approvals, and merge conflicts.

Official
Intermediate