feature-delivery

Coordinate feature delivery from Issue creation to reviewed PRs in GitHub workflows.

1|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/takuto277/levelup-study --skill feature-delivery-takuto277
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-delivery
Source: https://github.com/takuto277/levelup-study/tree/main/.cursor/skills/feature-delivery
Command: npx skills add https://github.com/takuto277/levelup-study --skill feature-delivery-takuto277

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan, implement, and review features through a structured, repeatable workflow that starts with an issue and ends with a reviewed PR.

Core Features & Use Cases

  • Issue-driven planning: Create and align issues with execution plans, traceable to implementation.
  • PR orchestration: Automate PR creation, self-review, and coordinated reviewer feedback.
  • Execution documentation: Maintain execution plans and validation steps as living artifacts.
  • Use Case: When a product team outlines a multi-task feature, this Skill guides the team from planning to merge with consistent checks.

Quick Start

Create an issue from your plan, then open a PR and complete the self-review following the described workflow.

Frequently Asked Questions about feature-delivery

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

FAQPage Schema
How do I orchestrate end-to-end feature delivery from issue creation to PR review?

Issue-driven feature delivery works by aligning GitHub issue creation with execution plans and traceable implementation. PR orchestration then automates PR creation, self-review, and coordinated reviewer feedback to maintain consistent checks.

How do I automate PR creation and self-review for GitHub workflows?

Automating PR creation and self-review is handled through PR orchestration within the feature delivery workflow. This process enforces a multi-step plan-to-PR transition, requiring documented execution plans and validation steps before reviewer feedback.

What is an issue-driven workflow for software development planning?

An issue-driven workflow creates and aligns GitHub issues with execution plans that are traceable to implementation. It ensures structured task planning and execution documentation are maintained as living artifacts throughout the feature delivery process.

Does this feature delivery workflow support multi-task feature planning on GitHub?

This feature delivery workflow supports multi-task feature planning on GitHub by guiding teams from planning to merge. It enforces a structured, repeatable workflow with consistent checks, self-review, and documented execution plans.

When do I need a structured workflow for issue creation and PR execution?

You need a structured workflow for issue creation and PR execution when a product team outlines multi-task features requiring repeatable plan-to-PR transitions. It enforces self-review and documented validation steps to maintain execution plan artifacts.