Menu
Interview to flesh out a plan/spec
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Create conventional git commits from all uncommitted changes. Extracts ticket numbers from branch names and uses conventional commit format.
Create conventional git commits from staged changes only. Extracts ticket numbers from branch names and uses conventional commit format.
Push current branch and create a GitHub pull request with proper formatting. Use when you have committed changes ready to be pushed and want to open a PR with a well-structured description.
Analyze and fix GitHub issues. Use when given a GitHub issue URL or number to investigate, understand the root cause, implement a fix, and verify the solution works.
Interview users in-depth to create detailed feature specifications. Use when gathering requirements for a new feature, understanding user needs, or creating PRDs. Asks probing questions about technical implementation, UI/UX, and edge cases.
Generate and maintain project documentation. Use when initializing docs for a new project, updating architecture docs, or creating feature specifications. Creates ai_docs/ and ai_specs/ folders with structured documentation.
Basé sur la classification professionnelle SOC
| name | interview |
| description | Interview to flesh out a plan/spec |
| allowed-tools | AskUserQuestion, Read, Glob, Grep, Write, Edit |
| argument-hint | [plan-file] |
Here's the current plan:
@$ARGUMENTS
Interview me in detail using the AskUserQuestion tool about literally anything: technical implementation, UI & UX, concerns, tradeoffs, etc. but make sure the questions are not obvious.
Be very in-depth and continue interviewing me continually until it's complete, then
write the spec back to $ARGUMENTS.
