create-spec

Guide a collaborative discussion to produce a project specification at .turbo/spec.md.

399|31|Updated Mar 11, 2026

Search Tags:#planning #project management #documentation #specification #requirements gathering

Ready to run

npx skills add https://github.com/tobihagemann/turbo --skill create-spec-tobihagemann

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-spec
Source: https://github.com/tobihagemann/turbo/tree/main/skills/create-spec
Command: npx skills add https://github.com/tobihagemann/turbo --skill create-spec-tobihagemann

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides users through a structured discussion to define project requirements and synthesizes the conversation into a comprehensive specification document, preventing scope creep and ensuring clarity before development begins.

Core Features & Use Cases

Guided Specification: Facilitates a collaborative process to flesh out project ideas.
Structured Output: Generates a .turbo/spec.md file detailing project vision, features, architecture, tech stack, and more.
Use Case: When starting a new feature, run this skill to discuss the problem, user needs, technical constraints, and desired MVP, resulting in a clear blueprint for development.

Quick Start

Use the create-spec skill to start planning the new user authentication module.

Frequently Asked Questions about create-spec

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

FAQPage Schema

How do I create a project specification document to prevent scope creep?▼

To create a project specification and prevent scope creep, this Skill guides you through a collaborative discussion that captures your vision and probes for details across users, features, and architecture, synthesizing the conversation into a structured spec.

What is the best way to gather requirements for an MVP before development begins?▼

Gathering requirements for an MVP involves discussing the problem, user needs, technical constraints, and desired features. This Skill facilitates that structured discussion to ensure clarity and produces a comprehensive blueprint before development begins.

How do I structure a project requirements document covering architecture and tech stack?▼

Structuring a project requirements document is achieved by synthesizing a guided discussion into a structured output. This Skill generates a specification file detailing your project vision, features, architecture, and tech stack.

Can I use a guided discussion to define project requirements for a new feature module?▼

Yes, you can use a guided discussion to define project requirements for a new feature module. This Skill facilitates a collaborative process to flesh out project ideas like an authentication module, capturing details to produce an actionable specification.

What should be included in a project specification to ensure development clarity?▼

A project specification for development clarity should include the project vision, user needs, features, architecture, and tech stack. This Skill probes for details across these key categories and synthesizes them into a structured, actionable spec.

Does this requirements gathering process output a file I can use for project management?▼

Yes, the requirements gathering process outputs a file for project management. It synthesizes the collaborative discussion into a comprehensive specification document saved as a `.turbo/spec.md` file, providing a clear blueprint for development.