メニュー
Pattern for creating hierarchical GitHub issue trees from phased project plans while checking for duplicate/overlapping issues
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/vamseeachanta/workspace-hub --skill staged-issue-tree-creation-with-deduplicationコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
Write outbound email and external messages in Vamsee Achanta's voice — a subtle offer to help, never bold or rash claims. Load before drafting ANY email, LinkedIn/Collide reply, proposal note, or outreach sent under his name.
Save/publish analysis or computation results from ANY ecosystem repo to Hugging Face as a queryable, viewer-renderable dataset. Use when the user wants to "save results to hugging face", "publish dataset to HF", "hugging face data saving", "save analysis results", "hf dataset", "make results queryable", or "render via datasets-server API". Reshapes nested results into flat parquet tables, writes a dataset card with a viewer `configs:` block and provenance, applies license/public-vs-private routing, enforces a domain data-quality gate (faithful-to-source != correct), publishes to `aceengineer/<repo>-<projection>`, and verifies via the datasets-server API.
Clone, create, fork, configure, and manage GitHub repositories. Manage remotes, secrets, releases, and workflows. Works with gh CLI or falls back to git + GitHub REST API via curl.
SOC 職業分類に基づく
| name | staged-issue-tree-creation-with-deduplication |
| description | Pattern for creating hierarchical GitHub issue trees from phased project plans while checking for duplicate/overlapping issues |
| version | 1.0.0 |
| source | auto-extracted |
| extracted | "2026-04-13T00:00:00.000Z" |
| metadata | {"tags":["github-issues","project-planning","deduplication","issue-management"]} |
When converting a phased project plan into GitHub issues: (1) Search for existing related issues first to identify overlaps and distinguish scope; (2) Gather local context (files, inventories, labels) to write informed issue descriptions; (3) Design the tree structure by clarifying which existing issues are distinct vs. which new parent/child issues are needed; (4) Assign consistent labels (reusing existing ones) and status markers (e.g., status:plan-review for newly created issues pending approval); (5) Create parent issue first, then batch child issues in parallel, then backlink them all. This prevents duplicate effort and ensures hierarchical consistency.