task-interview

Interviews users with structured questions to clarify task specifications and ambiguities.

2|Updated Sep 25, 2011
One-click install
npx skills add https://github.com/pokutuna/dotfiles --skill task-interview-pokutuna
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: task-interview
Source: https://github.com/pokutuna/dotfiles/tree/main/claude/skills/task-interview
Command: npx skills add https://github.com/pokutuna/dotfiles --skill task-interview-pokutuna

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Vague or incomplete task descriptions lead to misaligned implementations and wasted rework. This Skill systematically interviews you to surface hidden ambiguities in a plan or task before any code is written. ## Core Features & Use Cases - Structured Clarification Rounds: Uses the AskUserQuestion tool to ask 2-4 targeted questions per round, each with 2-4 options including pros and cons, covering product scope, architecture, UI/UX, edge cases, dependencies, and non-functional requirements. - Plan Integration: Reads the latest plan file or a task description passed as an argument, then writes decisions back into the plan file as they are resolved. - Decision Summary Output: Produces a decisions table (topic, decision, pros/cons, implementation notes) plus a prioritized list of next steps once all ambiguities are resolved or 10 rounds are reached. - Use Case: Before implementing a new feature, run this Skill on your draft plan to uncover unanswered questions about data storage, error handling, and concurrency, then receive a concrete specification ready for implementation. ## Quick Start Ask the assistant to interview you about the current plan or a task description to resolve all ambiguities and produce a final specification.

Frequently Asked Questions about task-interview

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I clarify a vague task description before implementation?

Run an interactive interview that asks targeted questions about scope, architecture, UI/UX, edge cases, and dependencies. Each question offers 2-4 options with pros and cons, and decisions are written back into your plan file until no ambiguities remain.

How does the task interview skill find the task to clarify?

It uses the text or file path passed as an argument first. If no argument is given, it reads the latest plan file from the current session. If neither exists, it asks you to create a plan or provide a task description.

What output does a requirements clarification interview produce?

It produces a decisions table listing each topic, the chosen decision, pros and cons, and implementation notes, followed by a numbered list of next steps. This summary serves as the finalized specification for implementation.

Is there a limit to how many interview rounds run?

Yes, the interview runs for a maximum of 10 rounds. It stops earlier if all ambiguities are resolved, then outputs the final decisions summary and next steps.

When should I not use an interactive task interview?

Avoid it for trivial or self-evident tasks where requirements are already clear, since the skill explicitly avoids obvious questions and is designed for non-trivial ambiguity. It also requires interactive user responses, so it does not fit fully automated pipelines.