This skill transforms feature specifications, requirements documents, or plans into well-structured GitHub issues. It chunks large features into small, testable issues, creates them via gh CLI, and adds them to the appropriate GitHub project with labels. Use when converting specs to actionable issues.
Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.
Quelldateien prüfen
Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.
This skill transforms feature specifications, requirements documents, or plans into well-structured GitHub issues. It chunks large features into small, testable issues, creates them via gh CLI, and adds them to the appropriate GitHub project with labels. Use when converting specs to actionable issues.
Parse feature specifications and create small, testable GitHub issues that are ready for development. Automatically create issues via gh CLI and add them to the appropriate project with proper labels and fields.
Provide the following:
Specification source - File path, pasted text, or plan file
## Description
Add migration for {description}.
## Acceptance Criteria- [ ] Migration file created
- [ ] UP migration works
- [ ] DOWN migration works
- [ ] SQLC queries updated
## Technical Notes- Migration name: `{name}`- Affected tables: {tables}
Filter/Search Enhancement Issue
## Description
Add {filter_name} filter to {endpoint} endpoint.
## Acceptance Criteria
- [ ] Filter parameter added to OpenAPI spec
- [ ] SQLC query updated with filter logic
- [ ] Handler processes filter correctly
- [ ] Empty filter returns all results
- [ ] Filter values validated
## Technical Notes
- Use `ANY(array)` pattern for multi-value filters
- Add to existing filter endpoint if applicable
</issue_templates>
<batch_creation_script>
Batch Issue Creation
For creating multiple issues from a markdown file:
#!/bin/bash# create_issues.sh
REPO="Owner/Repo"
PROJECT="ProjectName"
SYSTEM="Backend"
STATUS="Backlog"# Options: Backlog, Ready, In progress, In review, Done
PRIORITY="P1"# Options: P0, P1, P2, P3
SIZE="S"# Options: XS, S, M, L, XL# Find project number
PROJECT_NUM=$(gh project list --owner "Owner" --format json | jq -r '.projects[] | select(.title=="'"$PROJECT"'") | .number')
echo"Creating issues for $REPO, Project #$PROJECT_NUM"# Parse Issues.md and create each issue# (Implementation depends on file format)# Example: Create single issue
ISSUE_URL=$(gh issue create \
--repo "$REPO" \
--title "Issue title" \
--body "Issue body" \
--label "size: S,priority: High" \
2>&1 | grep -o 'https://.*')
echo"Created: $ISSUE_URL"# Add to project
gh project item-add "$PROJECT_NUM" --owner "Owner" --url "$ISSUE_URL"
</batch_creation_script>
Before creating issues:
Labels exist in repository (create if not)
Project exists and is accessible
System field exists in project
Status field exists in project (Backlog, Ready, In progress, In review, Done)
Priority field exists in project (P0, P1, P2, P3)
Size field exists in project (XS, S, M, L, XL)
Issues are properly sized (not too large)
Dependencies are documented
No duplicate issues exist
After creating issues, provide summary:
# Issue Creation Summary**Repository:** Owner/Repo
**Project:** ProjectName
**Total Issues Created:** X
| # | Title | Size | Priority | URL |
|---|-------|------|----------|-----|
| 1 | Issue title | S | High | https://... |
| 2 | Issue title | M | Medium | https://... |
## Next Steps1. Review created issues
2. Adjust priorities if needed
3. Assign to team members
4. Add to sprint/milestone
<success_criteria>
Issue creation is complete when:
All spec components converted to issues
Issues are appropriately sized
Labels applied correctly
Issues added to project
Project fields set (System, Status, Priority, Size)
Summary provided with all issue URLs
</success_criteria>
