skills.rest
Petelids
PetelidsCOMMUNITY
Explore all skills by this author →
GitHub

feature-pr-delivery

Organize end-to-end feature delivery with a docs-first workflow.

Updated Aug 23, 2026
Search Tags:#workflow#pull-request#feature-delivery#progress-tracking#plan-management#docs-first
One-click install
npx skills add https://github.com/Petelids/Sudoku --skill feature-pr-delivery
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: feature-pr-delivery
Source: https://github.com/Petelids/Sudoku/tree/main/skills/feature-pr-delivery
Command: npx skills add https://github.com/Petelids/Sudoku --skill feature-pr-delivery

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Delivers features through a documentation-first workflow: create a feature doc, open a PR, address reviews, add a plan, then execute tasks in priority order while updating progress.

Core Features & Use Cases

  • Documentation-first feature delivery: craft a feature spec, open a PR, incorporate feedback, and lock in a plan before implementation.
  • Structured execution: maintain a feature plan with prioritized tasks, dependencies, explicit statuses, and an execution log.
  • Progress discipline: commit and push updates to docs as work progresses, ensuring a single source of truth for the team.

Quick Start

Draft a feature document, open a PR, and create a plan file before starting implementation.

Frequently Asked Questions about feature-pr-delivery

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

FAQPage Schema
How do I manage feature delivery using a docs-first workflow?▼

Feature delivery via a docs-first workflow involves creating a feature spec, opening a PR, incorporating reviews, and locking in a plan before implementation. You maintain a feature plan with prioritized tasks and update progress through commits to ensure a single source of truth.

What is a docs-first pull request workflow for product management?▼

A docs-first pull request workflow requires drafting a feature document and opening a PR for review before any implementation begins. This ensures tracked planning and feedback are locked into a plan file before executing prioritized tasks.

How do I track feature progress and task execution in a structured plan?▼

You track feature progress by maintaining a feature plan file with prioritized tasks, dependencies, and explicit statuses. The workflow records commits and progress updates to docs as work progresses, ensuring an execution log and a single source of truth.

Can I use this feature delivery workflow for autonomous task continuation?▼

Yes, the feature delivery workflow supports autonomous continuation by enforcing a clear task-selection rule based on the prioritized list in the plan file. It records commits and progress updates to ensure autonomous execution follows the locked plan.

What's the best way to structure feature docs and plan files for PR reviews?▼

The best way to structure feature docs is using enforced outputs like docs/features/[feature].md for the spec and docs/features/[feature].plan.md for the plan. This maintains a single source of truth for PR reviews and structured execution.

Related Skills

Explore More Product & Management Skills→
christopher-busschristopher-buss
6

writing-plans

Generate executable implementation plans from feature specifications into dated docs/plans files.

Community
Advanced
lee-tolee-to
1.1k

ai-factory.implement

Execute plan tasks with state updates and progress persistence.

Community
Advanced
etylsarinetylsarin
59

git-workflow

Enforce feature-branch pull request workflows and prevent direct commits to main.

Community
Intermediate
BryceEWatsonBryceEWatson

spec-driven-dev

Coordinate feature development through SPEC, PLAN, and REVIEW templates.

Community
Advanced