interview
The user has provided input: $1
First, determine if this input is a file path or raw text:
- If it looks like a file path (contains
/or ends with.md,.txt, etc.), use the Read tool to read the file contents as the plan - If it's raw text (a description, idea, or plan written directly), treat it as the plan content directly
If raw text was provided (not a file):
- Generate a filename using the format:
PLAN-YYYY-MM-DD-<short-summary>.mdwhere<short-summary>is 2-4 lowercase words from the plan separated by hyphens (use bashdatecommand to get the date) - Create this file in the current working directory with the initial plan text
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).
More from robzolkos/zolkos-agent-skills
catchup
Catch up on codebase changes by reviewing the diff from master and reading relevant spec files.
9done
Reset the working directory for the next task by ensuring no uncommitted changes exist, then switching to the main branch and pulling latest.
8plan2json
Convert feature requirements into structured end-to-end test cases as JSON.
8discovery
Quick user-centric interview to capture requirements from a time-poor stakeholder.
8prime
Prime yourself on a codebase by listing files and reading the README.
7ship
Commit, run bin/ci, and open a PR if CI passes. Use when ready to ship changes.
6