create-issuelisted

Use when the user asks to create a GitHub issue, file a bug, request a feature, open a tracking issue, or break a feature into multiple sub-issues. Guides interactive issue drafting with structured templates, workspace-change attachment, dependency linking, and the optional `autonomous` label for the automated dev pipeline.
zxkane/autonomous-dev-team · ★ 20 · Code & Development · score 64

Install: claude install-skill zxkane/autonomous-dev-team

# Create GitHub Issue Create well-structured GitHub issues from user descriptions through interactive clarification. ## Repository Detection Detect the repository from the current git remote: ```bash REPO=$(gh repo view --json nameWithOwner -q '.nameWithOwner') # Splits into OWNER and REPO_NAME ``` If detection fails, ask the user for the target repository. ## Process ### Step 1: Understand the Request When the user describes a feature or bug, gather context through clarifying questions. Do NOT create the issue immediately. **For features, clarify:** - What is the user-facing goal? (not implementation details) - What are the acceptance criteria? (how to verify it works) - Are there UI/UX implications? - What existing functionality does this relate to? - Priority and scope constraints **For bugs, clarify:** - Steps to reproduce - Expected vs actual behavior - Environment (prod, staging, PR preview) - Severity (blocking, degraded, cosmetic) - Any error messages or logs Ask 2-3 focused questions per round. Stop when there is enough information to write a clear issue. ### Step 2: Draft the Issue Use the appropriate template based on issue type. For full template content, consult **`references/issue-templates.md`**. Both templates include these required sections: - **Summary** / **Motivation** (feature) or **Steps to Reproduce** (bug) - **Requirements** with checkboxes (feature) or **Expected/Actual Behavior** (bug) - **Testing Requirements** (mandatory TDD section: