skills.rest
euroconic
euroconicCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

feature-delivery

Automate feature delivery governance with enforced Git branch lifecycle rules and DELIVERY_TRACKER.md updates.

1|Updated Mar 26, 2026
Search Tags:#workflow#security#qa#branching#delivery#pr-lifecycle#delivery-tracker
One-click install
npx skills add https://github.com/euroconic/noter --skill feature-delivery-euroconic
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: feature-delivery
Source: https://github.com/euroconic/noter/tree/main/skills/feature-delivery
Command: npx skills add https://github.com/euroconic/noter --skill feature-delivery-euroconic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Governs and streamlines the feature delivery workflow by enforcing branching discipline, end-to-end checks, and delivery traceability during the DELIVER stage.

Core Features & Use Cases

  • Enforces a single active feature branch policy to prevent context divergence and conflicting work during delivery.
  • Defines a clear pre-merge checklist and automated gates (tests, QA, evaluation, and security spot-check) to qualify delivery readiness.
  • Keeps delivery visible with DELIVERY_TRACKER.md updates and a defined PR lifecycle workflow for auditor-friendly traceability.

Quick Start

Create a new feature-delivery plan, initialize a single feature branch named feat/short-description, and record the delivery in DELIVERY_TRACKER.md.

Frequently Asked Questions about feature-delivery

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

FAQPage Schema
How do I enforce a single active feature branch policy during delivery?▼

To enforce a single active feature branch policy during feature delivery, you establish a one-active-branch rule that prevents context divergence and conflicting work by restricting concurrent branches throughout the delivery lifecycle.

What pre-merge checks are required for feature delivery readiness?▼

Required pre-merge checks for feature delivery readiness include automated gates for tests, QA, evaluation, and security spot-checks, alongside a defined pre-merge checklist to qualify branches before merging.

How do I maintain delivery traceability across the PR lifecycle?▼

You maintain delivery traceability across the PR lifecycle by enforcing DELIVERY_TRACKER.md updates and following a single merged PR policy, ensuring auditor-friendly visibility throughout the feature delivery process.

What is the correct branching convention for feature delivery workflows?▼

The correct branching convention for feature delivery workflows requires initializing a single feature branch named using the format feat/short-description to enforce naming consistency and lifecycle governance.

Can I use this workflow without QA and security gates?▼

No, this feature delivery workflow mandates end-to-end checks across QA, EVAL, and security gates, applying predefined automated gates to qualify delivery readiness and ensure governance compliance.

Related Skills

Explore More Software Engineering Skills→
ByronWilliamsCPAByronWilliamsCPA
1

pr-prepare

Generate Markdown pull request descriptions from git context with conventional titles.

Official
Intermediate
Draft-OfficialDraft-Official

verification-before-completion

Execute verification commands to confirm tests and builds before task completion.

Official
Intermediate
dr-codedr-code

release-check

Run pre-release verification checks and write a versioned release assessment report.

Community
Advanced
zach-sourcezach-source

gitflow

Implement GitFlow branching with feature, release, and hotfix workflows.

Community
Intermediate