create-spec

Generate behavior-driven specifications from Linear issues, files, URLs, and codebase analysis.

4|Updated Oct 27, 2014

Search Tags:#testing #code analysis #documentation #specification #requirements #behavior-driven development

Ready to run

npx skills add https://github.com/B-Galati/dotfiles --skill create-spec-b-galati

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-spec
Source: https://github.com/B-Galati/dotfiles/tree/main/claude/skills/create-spec
Command: npx skills add https://github.com/B-Galati/dotfiles --skill create-spec-b-galati

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires get_issue, WebFetch, local-mr-diff-summarizer, deep-explore, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill transforms any requirement input into a structured, behavior-driven specification, ensuring clarity and testability for software development.

Core Features & Use Cases

Input Flexibility: Accepts Linear issues, free text, files, URLs, or conversation context.
Codebase Analysis: Explores the codebase to identify impacts and required changes.
Collaborative Spec Writing: Produces detailed specifications with toggleable behaviors mapped to tests.
Use Case: When a new feature request comes in via a Linear issue, this Skill analyzes the existing code, gathers relevant context, and generates a formal specification document with clear, testable behaviors.

Quick Start

Use the create-spec skill to formalize requirements for the 'add-user-authentication' feature based on the provided Linear issue 'SEC-123'.

Frequently Asked Questions about create-spec

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

FAQPage Schema

How do I generate behavior-driven specifications from a Linear issue?▼

Behavior-driven specifications formalize requirements into structured, testable behaviors. This skill generates them by exploring your codebase to identify impacts and mapping user requirements to toggleable behaviors for automated testing.

How do I write testable specs from free text, files, or URLs?▼

Writing testable specs from free text, files, or URLs involves analyzing the input context alongside codebase impacts. The skill processes these varied sources to output detailed specifications with toggleable behaviors for automated testing.

Do I need a specific environment setup to analyze codebase impacts for requirements?▼

Generating specifications for complex features involves exploring the codebase to identify impacts and gathering context from the input source. This skill maps the analyzed requirements into a formal specification document with clear, testable behaviors.

Can I use conversation context to create formal specifications for new features?▼

Yes, conversation context can be used to create formal specifications. The skill accepts conversation context as an input source, analyzing it alongside codebase impacts to produce structured, behavior-driven specifications with testable behaviors.

What's the best way to map user requirements to automated tests?▼

The best way to map user requirements to automated tests is by generating behavior-driven specifications with toggleable behaviors. This skill formalizes requirements and codebase impacts into detailed specs directly mapped to testable behaviors.

Why does requirement formalization require code exploration and web fetching?▼

Requirement formalization requires code exploration and web fetching to accurately identify codebase impacts and gather external context. These dependencies ensure the generated behavior-driven specifications reflect actual required changes and external user needs.