full-feature-workflow

Orchestrate end-to-end feature delivery across Jira, code changes, MR, and Slack.

4|Updated Apr 10, 2023
One-click install
npx skills add https://github.com/dudeofawesome/nix-config --skill full-feature-workflow
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: full-feature-workflow
Source: https://github.com/dudeofawesome/nix-config/tree/main/modules/presets/home-manager/paciolan/llms/skills/full-feature-workflow
Command: npx skills add https://github.com/dudeofawesome/nix-config --skill full-feature-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end feature workflow from intake to stakeholder notifications, reducing manual handoffs across Jira, code changes, MR, and Slack.

Core Features & Use Cases

  • Orchestrates a seven-step feature workflow: identify the spec, ensure a Jira story, implement changes, wait for review, commit and open MR, notify blame, and final reporting.
  • Supports resume semantics: if a step stalls, re-invocation resumes from the first incomplete step using stored context.
  • Delegates to specialized sub-skills (create-jira-item, commit-and-mr, notify-blame) to perform complex tasks, while enforcing safety and input validation.

Quick Start

Provide a Jira key, Confluence URL, file path, or plain description to start the end-to-end workflow.

Frequently Asked Questions about full-feature-workflow

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

FAQPage Schema
How do I automate the feature workflow from Jira to a merge request?▼

This orchestrator automates the feature workflow by taking a Jira key, Confluence URL, file path, or plain description and coordinating a seven-step delivery process ending in a merge request.

What is the best way to link Jira stories to code changes and merge requests?▼

The best way to link Jira stories to code changes is to use an orchestrator that coordinates the feature workflow, automatically identifying the spec, ensuring a Jira story exists, and managing the commit and MR process.

Can I resume a stalled feature workflow from an incomplete step?▼

Yes, you can resume a stalled feature workflow. The orchestrator uses resume semantics to re-invoke from the first incomplete step using stored context, preventing manual handoff delays.

Does the feature workflow orchestrator support Slack blame notifications?▼

Yes, the feature workflow orchestrator supports Slack blame notifications by delegating to specialized sub-skills to notify stakeholders automatically after committing and opening a merge request.

What inputs do I need to start the end-to-end feature delivery process?▼

To start the end-to-end feature delivery process, you need to provide a Jira key, a Confluence URL, a file path, or a plain text description of the feature.

Why does the orchestrator delegate to sub-skills for merge requests?▼

The orchestrator delegates to sub-skills like commit-and-mr and notify-blame to perform complex tasks safely, enforcing input validation while coordinating the broader Jira to merge request workflow.