// Transforms rough requirements into well-structured GitHub issues. Use when the user provides a vague idea, feature request, or problem description and wants to create a GitHub issue. Analyzes codebase, explores solution approaches, researches relevant libraries, and generates actionable issues using `gh` CLI.
Create or update a Routa Canvas artifact for the current task. Use when the user wants a live visual or interactive canvas generated from a Routa session.
Automate the Routa release preparation workflow from version sync through release note and blog generation. Use when the user wants to prepare, publish, or dry-run a Routa release.
Use this skill for creating, editing, and reviewing DOCX files, including generation, formatting, content controls, tracked changes, comments, accessibility checks, redaction, rendering, and diff-based QA workflows.
Use this skill for PDF generation, conversion, inspection, extraction, editing, form filling, OCR, redaction, or render comparison. Triggers include requests to create a PDF, convert Markdown or HTML or LaTeX or DOCX or PPTX to PDF, extract text or tables or images, fill or inspect forms, OCR scans, compare revisions, or redact content.
Use this skill as reference material when creating or editing presentation slide decks.
Use this skill for spreadsheet creation, editing, analysis, formatting, formula modeling, charting, or workbook review. Triggers include requests to create or modify an .xlsx file, build a model or tracker, format a workbook, add formulas or charts, or prepare a shareable spreadsheet deliverable.
| name | issue-enricher |
| description | Transforms rough requirements into well-structured GitHub issues. Use when the user provides a vague idea, feature request, or problem description and wants to create a GitHub issue. Analyzes codebase, explores solution approaches, researches relevant libraries, and generates actionable issues using `gh` CLI. |
| license | Complete terms in LICENSE.txt |
Extract from user input:
@file.yaml, existing code pathsIf the task is enriching an existing GitHub issue rather than creating a new one:
docs/issues/ as the local issue knowledge base when it is availableSearch the codebase to understand context:
- Existing patterns for similar features
- Related modules and their architecture
- Relevant configuration files
- Test patterns used in the project
- Existing local issue files under docs/issues/ that provide historical context
- Linked PR file changes for related GitHub issues (fetch via gh when needed)
When related historical GitHub issues are found, fetch their linked PR context before finalizing the analysis:
gh issue view <issue-number> --json number,title,url,closedByPullRequestsReferences
gh api repos/<owner>/<repo>/pulls/<pr-number>/files --paginate
Summarize:
patch hunksFor each potential approach, research:
Generate 2-3 distinct approaches when multiple solutions exist.
If one requirement actually contains multiple distinct features:
Use gh issue create with structured content:
gh issue create \
--repo {owner}/{repo} \
--title "Brief, action-oriented title" \
--body "$(cat <<'EOF'
# Problem
[1-2 sentences describing the core problem]
## Context
- Current behavior: ...
- Desired behavior: ...
- Related: #issue-number (if applicable)
## Proposed Approaches
### Approach 1: [Name]
**Libraries**: `package-name` (v1.x) - [brief description]
**Pros**:
- ...
**Cons**:
- ...
**Estimated effort**: Small/Medium/Large
### Approach 2: [Name]
...
## Recommendation
[Which approach to start with and why]
## Out of Scope
- [Explicitly excluded items]
## Labels
`enhancement`, `area:...`
EOF
)"
Each issue draft must include:
Related History section citing concrete prior issues or None found after searching docs/issues/Related PR File Context section when related issues have associated PRsRecommendation section choosing one approachOut of Scope sectionAfter creating the issue: