create-placeholder-issue

Creates a placeholder GitHub issue for a pending SDLC feature and promotes its directory to issue-numbered form.

11|1|Updated Jul 25, 2025

Search Tags:#automation #github #gh cli #issue #sdlc #cross-reference #feature promotion

Ready to run

npx skills add https://github.com/tomzx/agents --skill create-placeholder-issue-tomzx

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-placeholder-issue
Source: https://github.com/tomzx/agents/tree/main/skills/create-placeholder-issue
Command: npx skills add https://github.com/tomzx/agents --skill create-placeholder-issue-tomzx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Bottom-up SDLC features (created without a GitHub issue, using p-prefixed directories) lack issue tracking and consistent identifiers. This Skill creates a minimal placeholder issue, renames the feature directory to the issue number, and rewrites every FEAT- cross-reference so the feature becomes fully issue-driven. ## Core Features & Use Cases - Placeholder Issue Creation: Generates a minimal GitHub issue via the gh CLI, including requirements content when available, a visible placeholder note, and an HTML marker for later completion. - Directory Promotion: Renames p<seq>-<slug> directories to M-<slug> using git mv when tracked, across both repo and SDLC_DIR mirror locations. - Cross-Reference Rewriting: Replaces every FEAT-p<seq> token with FEAT-M across .md and .yml files using boundary-safe matching that avoids corrupting adjacent ids like FEAT-p20. - Use Case: After sync-sdlc creates a pending feature p2-billing from code analysis, run /create-placeholder-issue FEAT-p2 to create issue #137, rename the directory to 137-billing, and update all references. ## Quick Start Ask the agent to run /create-placeholder-issue for a pending feature such as FEAT-p1 to create its placeholder GitHub issue and promote the directory.

Frequently Asked Questions about create-placeholder-issue

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

FAQPage Schema

How do I create a GitHub issue for an existing SDLC feature?▼

Run /create-placeholder-issue with the feature id, token, or directory name, such as /create-placeholder-issue FEAT-p1. It creates a placeholder issue via the gh CLI, renames the p-prefixed directory to the issue number, and rewrites all FEAT- cross-references.

What is the difference between create-placeholder-issue and create-issue?▼

create-placeholder-issue promotes existing pending features created bottom-up (p-prefixed directories) by backing them with a minimal placeholder issue. create-issue works top-down, producing a full structured issue starting from a feature request.

Does create-placeholder-issue require the gh CLI?▼

Yes, it requires the GitHub gh CLI authenticated with write access to create issues in the target repository. It omits --repo so gh infers the repository from the working directory, and it never creates labels.

What happens if I run create-placeholder-issue twice on the same feature?▼

The skill is safe to re-run. A duplicate search finds the existing placeholder issue and resumes at the rename step instead of creating a second issue, and already-promoted features report already-issue-driven with no changes.

Why does the FEAT id rewrite not corrupt FEAT-p20 when replacing FEAT-p2?▼

The rewrite uses a boundary-safe pattern with a negative lookahead, matching FEAT-p2 only when not followed by another digit. This prevents partial matches inside longer identifiers like FEAT-p20 during the perl-based replacement.