feature-delivery-loop

Coordinate feature work from discovery to deployment with stage-gated approvals.

Updated Feb 17, 2026
One-click install
npx skills add https://github.com/aidanaden/sg-food-guide --skill feature-delivery-loop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-delivery-loop
Source: https://github.com/aidanaden/sg-food-guide/tree/main/.agents/skills/feature-delivery-loop
Command: npx skills add https://github.com/aidanaden/sg-food-guide --skill feature-delivery-loop

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Run an end-to-end feature/fix/PR workflow with requirement discovery, exhaustive clarification, explicit plan approval, Beads-tracked execution progress, and iterative review/fix loops until no bugs or edge cases remain.

Core Features & Use Cases

  • Beads tracking and issue integration to monitor progress
  • Stage-based workflow from intake to final approval and delivery
  • Explicit plan artifacts and review checkpoints to ensure quality

Quick Start

Create a plan artifact, await explicit approval, then execute the approved changes while tracking Beads progress.

Frequently Asked Questions about feature-delivery-loop

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

FAQPage Schema
How do I manage feature delivery from planning to deployment?

Feature delivery is managed by coordinating end-to-end work from discovery to deployment using explicit plan artifacts, Beads-tracked progress, and stage-gating approvals across intake, clarification, planning, execution, and review stages.

What is Beads tracking for feature workflow progress?

Beads tracking monitors execution progress throughout the feature delivery loop. It integrates with issue tracking to ensure development stages remain visible from initial intake through final approval and delivery.

How do I ensure code review catches bugs and edge cases during feature execution?

Code review catches bugs and edge cases by applying iterative review and fix loops until none remain. Comprehensive review checkpoints validate quality before stage-gating approvals allow deployment.

Does feature delivery require explicit plan approval before execution?

Feature delivery requires explicit plan approval before execution. You create a plan artifact, await explicit approval, and then execute approved changes while tracking Beads progress throughout the workflow.

Can I use this workflow for PR hardening and fixes, not just new features?

This workflow applies to product teams and engineers planning features, fixes, or PR hardening. It runs the same requirement discovery, clarification, planning, execution, and review stages regardless of work type.

What are the limitations of stage-gating approvals in feature delivery?

Stage-gating approvals limit feature delivery by requiring explicit plan artifacts and review checkpoints at each stage. Work cannot progress until approval is granted, ensuring quality but potentially slowing rapid iteration.