| name | q-setup-new-issue |
| description | Generate a custom /new-issue skill for your project. Ensures your issue tracker is configured via /q-which-tools, then writes a tailored skill that converts plain-English descriptions into well-structured issues. |
Setup /new-issue
You are generating a custom /new-issue skill for the user's project.
Required categories
This skill needs the following tools.json categories: issues
Process
-
Ensure tools are configured. Check if .quiddity/tools.json exists and
contains the issues category. If not, run /q-which-tools issues to
configure it.
-
Read the configuration. Load all available Quiddity context:
.quiddity/project.md — project structure, tech stack, issue templates.quiddity/process.md — issue workflow and conventions.quiddity/tools.json — extract the issues category
-
Ask skill-specific questions not covered by tools.json:
- Should the skill accept a description as an argument?
(e.g.,
/new-issue Add dark mode support)
- Do issues need acceptance criteria generated automatically?
- Any standard sections? (description, steps to reproduce, expected behavior)
- Any issue templates already in use?
- Auto-assign issues to the creator?
- For UI-related issues, should the skill generate ASCII wireframes to
illustrate the proposed change? (Great for making layout and component
ideas concrete before implementation.)
-
Generate the skill. Write a complete /new-issue SKILL.md to the
project's skills directory. The generated skill should:
- Accept a plain-English description (via
$ARGUMENTS or interactive prompt)
- Generate a structured issue with proper title, description, and acceptance
criteria based on the user's conventions
- Apply the right labels, priority, and milestone using the configured tracker
- Create the issue via MCP or CLI based on the tool in tools.json
- Return the issue identifier and URL
- Reference
.quiddity/tools.json for all tool-specific configuration
-
Show the generated skill to the user and ask for confirmation before
finalizing.
Generated skill template
The generated /new-issue skill should follow this general structure, adapted
to the user's specific tools:
---
name: new-issue
description: Create a new issue from a plain-English description.
argument-hint: "[description]"
---
# /new-issue
[Instructions tailored to the user's issue tracker, labels, states, etc.]
