feature-issues

Create GitHub parent and per-phase issues from completed workplans.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/oletizi/writingcontrol.org --skill feature-issues
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-issues
Source: https://github.com/oletizi/writingcontrol.org/tree/main/.claude/skills/feature-issues
Command: npx skills add https://github.com/oletizi/writingcontrol.org --skill feature-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It automates the creation of GitHub issues directly from a completed workplan, establishing a parent feature issue and per-phase implementation tasks to accelerate feature delivery and maintain traceability.

Core Features & Use Cases

  • Automated parent issue: generates a feature overview issue that references the PRD and workplan.
  • Per-phase tasks: creates one issue per workplan phase with clear acceptance criteria.
  • Workplan synchronization: updates the workplan with tracking links to all created issues.

Quick Start

Run the feature-issues skill after a workplan is ready to generate the parent feature issue, per-phase implementation issues, and updated tracking in the workplan.

Frequently Asked Questions about feature-issues

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

FAQPage Schema
How do I automate creating GitHub issues from a workplan?

Automating GitHub issue creation from a workplan generates a parent feature issue and per-phase implementation tasks. It extracts the slug from your workplan, builds linked issues on GitHub, and updates the workplan with tracking links.

How do I link a parent feature issue to implementation phases on GitHub?

Linking a parent feature issue to implementation phases creates one GitHub issue per workplan phase with clear acceptance criteria. The parent issue references the PRD and workplan, while tracking links are written back to the workplan document.

Do I need a specific folder structure to generate GitHub issues from a feature workplan?

Generating GitHub issues from a feature workplan requires maintaining files in docs/1.0/001-IN-PROGRESS/<slug> alongside PRDs. The workflow extracts the slug from this path to establish the parent issue and per-phase tasks deterministically.

What is the best way to maintain traceability between a PRD and GitHub issues?

Maintaining traceability between a PRD and GitHub issues is achieved by automating issue creation from the completed workplan. The parent issue references the PRD, and the workplan is updated with tracking links to all generated implementation tasks.

Why does workplan issue generation create a parent issue and separate phase tasks?

Workplan issue generation creates a parent issue for the feature overview and separate per-phase tasks to break down implementation. This deterministic workflow accelerates feature delivery by establishing clear acceptance criteria for each linked phase.

Can I synchronize GitHub issues with an existing workplan document?

Synchronizing GitHub issues with an existing workplan document updates the workplan with tracking links after creating the parent and per-phase issues. This ensures the document reflects the current state of all generated implementation tasks on GitHub.