con un clic
con un clic
Commit, run bin/ci, and open a PR if CI passes. Use when ready to ship changes.
Quick user-centric interview to capture requirements from a time-poor stakeholder.
Convert feature requirements into structured end-to-end test cases as JSON.
Catch up on codebase changes by reviewing the diff from master and reading relevant spec files.
Prime yourself on a codebase by listing files and reading the README.
Reset the working directory for the next task by ensuring no uncommitted changes exist, then switching to the main branch and pulling latest.
| name | interview |
| description | Interview me about the plan |
| argument-hint | ["file or text"] |
| model | opus |
| disable-model-invocation | true |
The user has provided input: $1
First, determine if this input is a file path or raw text:
/ or ends with .md, .txt, etc.), use the Read tool to read the file contents as the planIf raw text was provided (not a file):
PLAN-YYYY-MM-DD-<short-summary>.md where <short-summary> is 2-4 lowercase words from the plan separated by hyphens (use bash date command to get the date)Then 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 final spec to the file (either the original file if a file was provided, or the newly created timestamped file if text was provided).