メニュー
Run the full Quiddity setup flow. Discovers your process and tools, then generates custom /new-issue, /next-task, and /approve skills for your project.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Scan the current project and create a summary of its structure, important files, and conventions in .quiddity/project.md.
Generate a custom /next-task skill for your project. Ensures your issue tracker, source control, and CI are configured via /q-which-tools, then writes a tailored skill that picks up the next task, implements it, and opens a PR.
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.
Walk through the tools in .quiddity/tools.json and help install any missing CLIs or MCPs. Run /q-which-tools first if tools.json doesn't exist.
Discover what tools a project uses and save the configuration to .quiddity/tools.json. Pass category names as arguments (e.g., /q-which-tools issues source-control).
Generate a custom /approve skill for your project. Ensures your source control, CI, and PR conventions are configured via /q-which-tools, then writes a tailored skill that verifies checks and merges approved PRs.
| name | q-setup |
| description | Run the full Quiddity setup flow. Discovers your process and tools, then generates custom /new-issue, /next-task, and /approve skills for your project. |
You are running the full Quiddity setup flow for the user's project. This will discover their process and tools, then generate all three build-loop skills.
Welcome the user. Briefly explain what Quiddity does: it will scan their
project, learn about their development process and tools, set up CLIs and
MCPs, then generate three custom skills (/new-issue, /next-task, /approve) tailored to their
project.
Run /q-scan-project to scan the project structure. This documents key
files, tech stack, conventions, and project layout in .quiddity/project.md.
Run /q-which-process to discover the user's SDLC. This captures their
branching strategy, code review process, issue workflow, and other conventions
in .quiddity/process.md. It can reference project.md for context.
Run /q-which-tools with all categories needed across the three skills:
/q-which-tools issues source-control ci pr
Because /q-which-process has already run, /q-which-tools can reference
.quiddity/process.md to pre-fill answers and ask smarter questions.
Run /q-setup-tools to walk through CLI and MCP setup for each tool discovered in the previous step. This checks what's already installed and helps set up anything missing.
Run /q-setup-new-issue to generate the /new-issue skill.
Since project.md, process.md, and tools.json are already populated, this
will skip the interviews and go straight to skill-specific questions.
Run /q-setup-next-task to generate the /next-task skill.
Run /q-setup-approve to generate the /approve skill.
Summarize. Show the user what was generated:
.quiddity/project.md, .quiddity/process.md, and .quiddity/tools.json/new-issue [description] — create a new issue/next-task — pick up and implement the next task/approve [pr-number] — merge an approved PR.quiddity/ and the generated skills to source
control so the whole team shares the same configuration