interview
Scannednpx machina-cli add skill robzolkos/zolkos-agent-skills/interview --openclawThe 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).
Source
git clone https://github.com/robzolkos/zolkos-agent-skills/blob/master/skills/interview/SKILL.mdView on GitHub Overview
This skill conducts a thorough, iterative interview to sharpen a plan. It accepts either a file path or raw text, prompts with non-obvious, in-depth questions, and captures insights to write a final spec into a timestamped PLAN file.
How This Skill Works
The skill first detects whether the input is a file path or raw text. If raw text is provided, it generates a PLAN-YYYY-MM-DD-<short-summary>.md file name, creates the file in the current directory, and seeds it with the initial plan text. It then uses AskUserQuestion to interview you in depth—exploring technical details, tradeoffs, UI/UX, and risks—continuing until the plan is fully specified, after which it writes the final spec to the appropriate file (original or newly created).
When to Use It
- You have a rough plan and want a thorough, non-obvious interrogation to surface gaps and constraints.
- You need a formal, shareable plan document created from brainstorming notes or an outline.
- You’re coordinating cross-disciplinary work and want diverse questions to align stakeholders.
- You want traceable questions/answers that document decisions and rationale for future audits.
- You’re refining a plan iteratively and require a final spec saved to a timestamped file for versioning.
Quick Start
- Step 1: Provide either a raw plan description or a file path to an existing plan.
- Step 2: The system generates a timestamped PLAN file if needed and begins in-depth questioning via AskUserQuestion.
- Step 3: Complete the interview and let the tool write the final spec to the PLAN file.
Best Practices
- Provide a clear initial goal in the plan to anchor the interview and avoid drift.
- Encourage the interviewer to probe edge cases, failure modes, and data requirements.
- Document decisions, rationale, and assumptions as they arise during the interview.
- Use the generated PLAN file name as a living document for versioned updates.
- Review the final spec against acceptance criteria and capture any remaining gaps.
Example Use Cases
- Interview a product plan to validate scope, milestones, and success metrics before a sprint.
- Interview an architecture plan to surface scalability, security, and integration risks.
- Interview a research plan to define hypotheses, data collection, and analysis methods.
- Interview a marketing launch plan to align channels, timelines, and budget constraints.
- Interview an event planning plan to map logistics, vendors, and contingency plans.
