superplane-issue-logger
SuperPlane Issue Logger
Use this skill when a user describes an improvement, bug, or request in natural language. You will: (1) research and understand it in SuperPlane context, (2) classify issue type, (3) propose title and body in tmp/pm_logger, and (4) optionally create the issue on GitHub with correct labels.
Reference: docs/contributing/ (issue-tracking, quality, pull-requests, etc.), https://docs.superplane.com/ when relevant.
1. Research and understanding
- Context: Use docs/contributing/ (issue-tracking, quality, pull-requests, integrations, component-design) and, when relevant, https://docs.superplane.com/ (product behavior, UX).
- Clarification: If the description is vague (e.g. "improve the canvas" or "fix the button"), prompt the user for: what exactly is wrong or desired, where in the app it happens, expected vs actual behavior, and (for bugs) steps to reproduce.
- Scope: One issue per draft. If the user describes multiple items, ask which one to capture first or create separate drafts.
2. Issue type classification
Map the user's description to exactly one of:
More from superplanehq/superplane
prd-writing
Write and review concise product requirement documents for this repository. Use when the user asks to create, improve, or validate a PRD, scope a feature, or document goals, non-goals, requirements, risks, and metrics.
1superplane-changelog
When generating a SuperPlane changelog from merged commits. Use for "what's new" summaries with new integrations, new components/triggers, improvements, security updates, and bug fixes. Output is user-focused markdown in tmp/.
1