interview

Convert rough ideas into actionable specifications through structured elicitation and constraint enforcement.

7|2|Updated Nov 30, 2025

Search Tags:#specification #design review #architecture planning #requirements elicitation #constraint management #assumption audit #business idea validation

Ready to run

npx skills add https://github.com/ajbmachon/ajbm-skills --skill interview-ajbmachon

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: interview
Source: https://github.com/ajbmachon/ajbm-skills/tree/main/plugins/interview/skills/interview
Command: npx skills add https://github.com/ajbmachon/ajbm-skills --skill interview-ajbmachon

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It prevents costly misalignment by transforming vague ideas into clear, constraint-respecting specs through structured elicitation, assumption surfacing, and research-backed challenge.

Core Features & Use Cases

Structured interview workflows: QuickClarify for small ambiguities, plus full workflows (DevSpec, BusinessIdea, DocumentDraft, DesignReview, Ideation, DevilsAdvocate) for deeper planning.
Assumption audit + constraint enforcement: Captures user-imposed requirements in a Constraint Registry, then verifies major decisions against them to avoid drift.
Ego-free challenge and convergence: Uses Devil’s Advocate to stress-test ideas, then converges to a shared, implementation-ready understanding with a progressive working log.

Quick Start

Use this skill by asking it to turn your idea into a spec with a devil’s advocate challenge and then a constraint-confirmed implementation plan.

Frequently Asked Questions about interview

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

FAQPage Schema

How do I turn a rough business idea into an implementation-ready specification?▼

To turn a rough idea into an implementation-ready specification, use structured elicitation with mirroring and assumption surfacing. This process captures constraints and applies a Devil's Advocate challenge to stress-test the concept before generating a progressive working log.

What is the best way to run a design review that captures hidden assumptions?▼

A design review that captures hidden assumptions uses structured probing questions and assumption audits. This approach surfaces unstated requirements, enforces constraint convergence, and prevents costly misalignment before implementation begins.

How do you stress-test a feature plan before starting development?▼

To stress-test a feature plan, apply a Devil's Advocate workflow that challenges the architecture and business logic. This method captures constraints in a registry and blocks recommendations that conflict with stated requirements.

Does structured requirements elicitation work for non-technical domains?▼

Structured requirements elicitation works for non-technical domains like business case development and document drafting. It uses mirroring and probing to extract clear constraints and converges on a shared understanding across both technical and non-technical contexts.

Why does my project drift away from the original business requirements?▼

Project drift happens when unstated assumptions override business requirements. An assumption audit captures these constraints in a registry and uses a verification gate to block any implementation recommendations that conflict with your stated needs.