Loading...
Loading...
Found 30 Skills
Strategic requirement roadmap with iterative decomposition and issue creation. Outputs roadmap.md (human-readable, single source) + issues.jsonl (machine-executable). Handoff to team-planex.
This skill is used when users mention "create issue", "register bug", "create task", "issue list", "my tasks", "assigned issues", "update issue", "change issue status", "search issues", "ticket", "issue", "bug report", etc. Provides Redmine issue management functionality.
Report a bug in the compound-engineering plugin
This skill should be used when the user asks to "create an issue", "file a bug", "create a feature request", "open a GitHub issue", "report a bug", "request a feature", "create a task", "break this into issues", or describes a feature/bug they want tracked in GitHub. Guides interactive issue creation with structured templates, workspace change attachment, and optional autonomous label for the automated pipeline.
Create Linear tickets or GitHub issues following n8n conventions. Use when the user asks to create a ticket, file a bug, open an issue, or says /create-issue.
Report a bug in the compound-engineering plugin
Create Linear issues. Use when creating bugs, tasks, or feature requests.
Create GitHub issues following Pollinations team conventions. Use when asked to create issues, track work, or plan features.
Run /check-landing, then create GitHub issues for all findings. Issues are created with priority labels and structured format. Use /fix-landing instead if you want to fix issues immediately.
Use when the user asks to create a GitHub issue from the current conversation context (e.g., "new issue", "create issue", "file an issue", bug/feature request) with a target repo given or auto-detected, and gh CLI is available/authenticated.
Run /check-posthog, then create GitHub issues for all findings. Each finding becomes a separate, actionable issue with clear acceptance criteria. Invoke for: PostHog audit to issues, analytics backlog creation.
Create GitHub issues using data-driven templates. Supports any issue type via configurable template configs. Use when the user asks to create a GitHub ticket, issue, or support ticket, or when they want to add a new issue template.