skills.rest
addisonbeck
addisonbeckCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

full-lifecycle-delivery

Orchestrate five-phase delivery from Jira tickets to validated pull requests.

Updated Mar 29, 2024
Search Tags:#orchestration#jira#pull-request#ci-validation#phased-delivery#team-coordination#roster-management
One-click install
npx skills add https://github.com/addisonbeck/nix --skill full-lifecycle-delivery
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: full-lifecycle-delivery
Source: https://github.com/addisonbeck/nix/tree/main/bobert/skills/full-lifecycle-delivery
Command: npx skills add https://github.com/addisonbeck/nix --skill full-lifecycle-delivery

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestration playbook for taking work from input (Jira ticket, memory stub, or prompt) through intake, research/design, implementation, finalization, and publishing to a validated PR. Defines team composition (11 work agents + 5 phase coordinators), phase-by-phase workflow, PhaseContext/PhaseResult protocol, and completion criteria for full-lifecycle delivery. Use when asked to research, design, and publish a validated PR from a Jira ticket, or when prompted to use Task Group A.

Core Features & Use Cases

  • Orchestrated five-phase delivery: intake, research/design, implementation, finalization, publishing with coordination.
  • Dynamic roster management and autonomous phase execution via PhaseContext and PhaseResult protocol.
  • Memory and retro continuity via dedicated agents to track TODOs and war stories.

Quick Start

Provide your initial input (Jira, memory stub, or prompt) to Bobert and initiate Phase 0 Intake and follow the PhaseContext-led roster protocol.

Frequently Asked Questions about full-lifecycle-delivery

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

FAQPage Schema
How do I automate end-to-end delivery from a Jira ticket to a validated pull request?▼

Automated end-to-end delivery from a Jira ticket to a validated pull request uses a phased team model to orchestrate intake, research, implementation, and publishing. It applies a PhaseContext protocol to assemble rosters and spawn agents.

What is phased delivery orchestration for software development?▼

Phased delivery orchestration coordinates work across five stages: intake, research and design, implementation, finalization, and publishing. It governs progress using a PhaseContext and PhaseResult protocol with deterministic team rosters.

Can I use plain text prompts instead of Jira tickets for automated pull request generation?▼

Yes, automated pull request generation accepts Jira tickets, memory stubs, or plain prompts as initial input. The orchestration playbook processes any of these formats through Phase 0 Intake to begin the workflow.

How does CI validation work within automated phased team coordination?▼

CI validation within phased team coordination acts as an automated quality gate during the finalization and publishing stages. It ensures the validated PR meets deterministic completion criteria before the lifecycle concludes.

Do I need a specific team roster setup for autonomous phase execution?▼

Autonomous phase execution uses a predefined team composition of 11 work agents and 5 phase coordinators. You do not need manual roster setup; the PhaseContext protocol dynamically assembles the required agents.

Related Skills

Explore More Product & Management Skills→
Leep-GHLeep-GH

init-mode

Propose a project roster and create the team structure after user confirmation.

Community
Intermediate
shogo-labsshogo-labs
12

github-ops

Aggregate GitHub pull requests, issues, and CI status onto a canvas dashboard.

Official
Advanced
jusleejuslee
2

verify-phase

Run all phase quality gates and report pass/fail results.

Community
Advanced
youssefKadaouiAbbassiyoussefKadaouiAbbassi

team-do

Create and manage agent teams for parallel task execution across multiple files.

Community
Advanced