workflow

Orchestrate a unified delivery pipeline with branch and PR continuity across development phases.

1|Updated Jul 1, 2026
One-click install
npx skills add https://github.com/marcuskrogh/skills --skill workflow-marcuskrogh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflow
Source: https://github.com/marcuskrogh/skills/tree/main/skills/workflow
Command: npx skills add https://github.com/marcuskrogh/skills --skill workflow-marcuskrogh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill solves the fragmentation of development workflows by providing a shared contract for feature work, bug fixes, and post-ship iterations, ensuring continuity across the entire delivery lifecycle.

Core Features & Use Cases

  • Closed-Loop Delivery: Maintains a single delivery branch and PR per task from definition through to final ship, preventing PR sprawl.
  • Pipeline Orchestration: Provides standardized handoff rules and continuation keywords like next and ship to automate transitions between research, modeling, implementation, and review.
  • Use Case: When working on a complex feature, use this Skill to ensure that research, planning, and implementation artifacts are all linked to the same task and PR, resulting in a clean, single-merge deployment.

Quick Start

Invoke the workflow skill to initialize the delivery pipeline for your current task by referencing the active issue key.

Frequently Asked Questions about workflow

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

FAQPage Schema
How do I maintain a single delivery branch and PR across research, implementation, and shipping phases?

A closed-loop delivery pipeline enforces branch and PR continuity per task, linking research, definition, and implementation artifacts to prevent PR sprawl and ensure a clean, single-merge deployment.

How do I automate transitions between software delivery phases like modeling and review?

Pipeline orchestration uses standardized handoff rules and continuation keywords like next and ship to automate transitions between research, modeling, implementation, and review phases in a delivery pipeline.

Does this delivery pipeline approach support both feature development and bug remediation?

Yes, the closed-loop delivery pipeline applies to feature development, bug remediation, and post-ship iteration cycles, providing a shared contract for continuity across the entire software delivery lifecycle.

What is the best way to sync issue tracker data with markdown decision logs during software development?

A standardized delivery pipeline satisfies requirements for tracker synchronization and markdown-based decision logging by orchestrating unified pipeline handoffs linked to an active issue key.

How do I initialize a closed-loop delivery pipeline for my current development task?

Invoke the workflow skill to initialize the delivery pipeline for your current task by referencing the active issue key, which sets up the standardized branch and PR continuity automatically.

Can I use this pipeline orchestration for post-ship iteration cycles in professional engineering environments?

Yes, the pipeline orchestrates post-ship iteration cycles within professional engineering environments by applying standardized handoff rules and closed-loop PR management to maintain task continuity.