interview

Sterne7

Forks0

Aktualisiert23. Juni 2026 um 15:27

Interview the user deeply about a plan, probing technical implementation, UI/UX, risks, tradeoffs, and missing decisions before writing or refining a spec. Use when the user says "interview me" or asks to be questioned about a plan.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

SDiamante13

SDiamante13/dotfiles

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

ProjektmanagementspezialistenWirtschafts- und Finanzberufe·SOC 13-1082

SKILL.md

readonly

name	interview
description	Interview the user deeply about a plan, probing technical implementation, UI/UX, risks, tradeoffs, and missing decisions before writing or refining a spec. Use when the user says "interview me" or asks to be questioned about a plan.

Read the plan file and interview me using the AskUserQuestion tool.

Ask about: technical implementation, UI/UX, concerns, tradeoffs.

Make sure the questions are not obvious. Be very in-depth and continue until it's complete and write the spec.

Mehr aus diesem Repository

gleiches Repository

review-plan

SDiamante13/dotfiles

XP-style plan review that identifies gaps, hidden assumptions, and critical misses. Triggers on 'review the plan', 'check the plan', 'audit the plan'. Reviews plans for YAGNI violations, missing feedback loops, and over-engineering.

2026-06-287

review

SDiamante13/dotfiles

Comprehensive code review for quality, security, performance. Triggers on 'review code', 'code review', 'check this PR', 'audit code'.

2026-06-287

tidy

SDiamante13/dotfiles

TDD Production Code Refactoring Process. Triggers on 'tidy up', 'tidy this', 'clean up code'. Use for refactoring production code with test coverage.

2026-06-287

tw-codebase-archaeology

SDiamante13/dotfiles

Systematically explore an unfamiliar codebase and build a reusable architecture summary. Use for repo onboarding, understanding legacy or inherited code, mapping architecture before a migration or refactor, tracing a bug or feature path, or answering "what does this project do?". Documentation-first, then data flow — ends in a concise technical architecture summary with file:line evidence, not a raw file dump.

2026-06-287

tw-codebase-doctrine

SDiamante13/dotfiles

Compile deep repository evidence into artifact-bound correctness doctrine — authority/law/proof maps, owned invariants, failure archaeology, and the strongest durable destination for each piece of knowledge, plus an optional minimal repository-specific skill portfolio. Use when the user wants both deep codebase understanding AND durable doctrine, knowledge routing, or repo-specific skill recommendations. Research discoverable facts before asking. Read-only. Not for quick onboarding, one isolated invariant, ordinary implementation, generic review, or direct skill creation.

2026-06-287

tw-fresh-eyes-blunder-pass

SDiamante13/dotfiles

Run a targeted fresh-eyes blunder pass over code, specs, plans, reviews, closure gates, or skill edits. Use when asked to reread with fresh eyes, find obvious bugs, catch mistakes/oversights/omissions, check for embarrassing misses, or do a second independent pass before closure. Use it as the final falsification/check pass for another workflow, not as a substitute for implementation or verification.

2026-06-287

Jeden Skill mit einem Klick ausführen