technical-intakelisted

Turn a client's half-formed software idea into a developer-ready specification. Use when anyone says "I want to build something," "I have an app idea," "we need a tool that does X," or asks for help with technical requirements gathering or project scoping. Also triggers on: "help me scope this," "turn this into a spec," "my client needs a build plan," or any vague product description from a non-technical person. Runs a 25-question adaptive interview (5 rounds x 5), silently calibrates to the client's technical level, detects goal drift, and produces five outputs: a Technical Specification, an implementation prompt, an opt-in React UI mockup, ranked Claude tool recommendations, and a ready-to-install project style. Covers web apps, SaaS, mobile, automation, and data pipelines. The go-to skill for developers, consultants, and agencies turning client conversations into code.
Method-Communications/technical-intake · ★ 0 · Web & Frontend · score 70

Install: claude install-skill Method-Communications/technical-intake

# Technical Intake > Turn a vague idea into a spec, a prompt, a UI mockup, a tool kit, and a custom style — in one conversation. --- ## What This Skill Does Most clients can't describe what they want to build — not because they don't know, but because they don't have the vocabulary. This skill bridges that gap. It runs a structured, adaptive interview that feels like a smart conversation, not a form. By the end, both parties are aligned, scope is locked, and five production-ready outputs are generated. **Outputs:** 1. **Technical Specification Document** (markdown) — with screen inventory + user flow map 2. **Implementation Prompt** — ready to paste into any LLM for code generation 3. **React/HTML UI Mockup** — a working visual skeleton of the primary user flow 4. **Tool Recommendations** — personalised Claude ecosystem setup for the project 5. **Project Style** — a custom Claude style tuned to the project's communication needs **Domains covered:** Web apps / SaaS · Mobile apps · Automation & bots · Data pipelines & dashboards **Tone:** Warm, clear, non-technical language. Translate everything the client says into structured requirements internally, but never talk "dev" at them. --- ## Reference Files Load on demand — not all at once. The right file at the right moment, nothing more. | File | When to Load | |------|-------------| | `references/domain-probes.md` | Round 1 signals a specific domain (e-commerce, scheduling, SaaS, etc.) | | `references/stack-defaults.m