skills.rest
team-attention
team-attentionOFFICIAL
Explore all skills by this author →
WebsiteGitHub

open

Generate a Draft PR from a validated spec using a PR body template.

171|23|Updated Jan 21, 2026
Search Tags:#automation#spec-driven#branch-management#pull-request#draft-pr#gh-cli
One-click install
npx skills add https://github.com/team-attention/hoyeon --skill open
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: open
Source: https://github.com/team-attention/hoyeon/tree/main/skills/open
Command: npx skills add https://github.com/team-attention/hoyeon --skill open

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill automates turning a formal Spec into a Draft PR, ensuring a single source of truth and consistent PR metadata for development work.

Core Features & Use Cases

  • Spec-driven PR creation: Generate a Draft PR directly from a given spec file (e.g., specs/user-auth.md).
  • PR body templating: Apply a standard PR body template that references the spec and summarizes planned work.
  • Workflow automation: Validate spec existence, create the feat/* branch, and push a Draft PR ready for review.
  • Use Case: When starting work from a formal spec, open a Draft PR that captures the plan and aligns stakeholders.

Quick Start

Use the open skill to draft a PR from specs/<name>.md and apply the PR body template.

Frequently Asked Questions about open

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

FAQPage Schema
How do I create a draft PR from a spec file?▼

Creating a draft PR from a spec file requires a validated spec at specs/<name>.md and an available pr-body-template. The workflow validates the spec, creates a feat/* branch, and pushes a draft PR ready for review.

What is a spec-driven pull request workflow?▼

Spec-driven pull request workflow establishes a single source of truth by generating a draft PR directly from a formal spec. It uses a PR body template to capture the plan and align stakeholders before development begins.

Do I need gh CLI setup to automate draft PR creation?▼

Yes, you need gh CLI setup to automate draft PR creation. The workflow relies on gh CLI to validate spec existence, create the feat/* branch, and push the draft PR with standard metadata to your repository.

Can I use a PR body template with spec-driven branch management?▼

Yes, you can use a PR body template with spec-driven branch management. The workflow applies a standard template that references the spec file and summarizes planned work to ensure consistent PR metadata across development.

What's the best way to align stakeholders before starting development work?▼

Opening a draft PR from a validated spec is the best way to align stakeholders. This captures the planned work and references the spec as a single source of truth, allowing reviewers to provide feedback before implementation.

Why does my spec-driven draft PR require a specific file path?▼

Your spec-driven draft PR requires the file path specs/<name>.md to validate spec existence and establish a single source of truth. The workflow checks this path before creating the feat/* branch and applying the PR body template.

Related Skills

Explore More Software Engineering Skills→
IKatsubaIKatsuba
1

spec:design

Generate a structured design document from requirements and research files.

Community
Advanced
gqf2008gqf2008

github-pr-workflow

Automate GitHub pull request lifecycle from branch creation to merge.

Community
Advanced
DayMoonDevelopmentDayMoonDevelopment
68

pull-request

Create a pull request for a monorepo sibling and link it to a Linear issue.

Official
Advanced
brandonalfredbrandonalfred
2

draft-pr

Create and push draft pull requests from GitHub feature branches.

Community
Intermediate