Agent skill
taskstoissues
Convert user stories to GitHub issues. Use when ready to create issues. Triggers on: create github issues, export to github, generate issues.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/taskstoissues
SKILL.md
GitHub Issues Generator
Convert user stories from tasks.md into GitHub issues.
The Job
- Read tasks.md
- Parse user stories
- Generate GitHub issues with
ghCLI - Link dependencies
Prerequisites
- GitHub CLI (
gh) installed and authenticated - Git repository with GitHub remote
- tasks.md exists with user stories
Issue Format
For each user story, create issue with:
Title: [US-XXX] Story Title
Body:
## Description
[Story description]
## Acceptance Criteria
- [ ] Criterion 1
- [ ] Criterion 2
- [ ] Typecheck passes
- [ ] Tests pass
## Dependencies
#123 (if US-001 already exists as issue #123)
## Phase
Foundation / Stories / Polish
## Priority
High / Medium / Low
---
From: tasks.md
Story ID: US-XXX
Labels:
user-storypriority-high/priority-medium/priority-low- Domain-specific:
database,api,ui,security, etc.
Execution
# Dry run first
relentless issues --feature NNN-feature --dry-run
# Create issues
relentless issues --feature NNN-feature
# Create all issues (including completed)
relentless issues --feature NNN-feature --all
Mapping
- Extract story ID, title, description, acceptance criteria
- Detect domain from description (api, database, ui, etc.)
- Map priority from tasks.md
- Create dependencies based on US dependencies
Notes
- Dry run first to preview
- Issues created in dependency order
- Issue numbers used for dependency linking
- Only creates issues for incomplete stories (unless --all)
- See relentless CLI for actual implementation
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?