skills.rest
OpenElementsLabs
OpenElementsLabsOFFICIAL
Explore all skills by this author →
WebsiteGitHub

spec-create

Generate design.md and behaviors.md from GitHub issues or briefs.

Updated Mar 7, 2026
Search Tags:#design#planning#collaboration#specification#feature#bug-fix
One-click install
npx skills add https://github.com/OpenElementsLabs/claude-base --skill spec-create-openelementslabs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-create
Source: https://github.com/OpenElementsLabs/claude-base/tree/main/claude-project-base/skills/spec-create
Command: npx skills add https://github.com/OpenElementsLabs/claude-base --skill spec-create-openelementslabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams convert vague ideas into precise design documents and behavioral scenarios, reducing ambiguity before implementation.

Core Features & Use Cases

  • Generates a design.md (technical design) and behaviors.md (given-when-then scenarios) in a dedicated spec folder.
  • Starting point from GitHub issue or free-text description.
  • Interactive discussion to refine requirements, acceptance criteria, and approach.

Quick Start

Provide a GitHub issue URL or a description and I will draft the initial design and behavioral specs.

Frequently Asked Questions about spec-create

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

FAQPage Schema
How do I generate a design document and behavioral scenarios from a GitHub issue?▼

To generate a design document from a GitHub issue, provide the issue URL to initiate an interactive discussion that refines requirements and produces a design.md and behaviors.md in a dedicated spec folder.

What is a spec-driven workflow for planning software features?▼

A spec-driven workflow formalizes feature planning by converting vague ideas into structured design documents and given-when-then behavioral scenarios, reducing ambiguity before implementation begins.

Can I create acceptance criteria for a bug fix using a descriptive brief?▼

Yes, you can create acceptance criteria for a bug fix by providing a free-text descriptive brief, which initiates an interactive discussion to refine the implementation approach and formalize the requirements.

Does this feature planning method require interactive discussion to refine requirements?▼

Yes, this feature planning method requires interactive discussion to accurately refine requirements, define acceptance criteria, and establish the implementation approach from your initial issue or brief.

What is the best way to structure technical design and behavior files for a new feature?▼

The best way to structure technical design and behavior files is using a spec-driven workflow that generates a design.md for technical design and a behaviors.md for given-when-then scenarios within a dedicated spec folder.

When do I need to formalize requirements into design and behavior specifications?▼

You need to formalize requirements into design and behavior specifications when starting a new feature or bug fix from a vague idea or issue, ensuring precise documentation and reduced ambiguity before implementation.

Related Skills

Explore More Software Engineering Skills→
openakitaopenakita
2.0k

submit-skill-repo

Submit a GitHub repository URL to the OpenAkita Skill Store for indexing.

Community
Basic
dfrysingerdfrysinger
36

test

Run acceptance tests against implemented code and present pass/fail results.

Community
Advanced
Progery222Progery222

github-project-management

Automate GitHub issue management, project board synchronization, and sprint planning.

Community
Intermediate
ConradmakerConradmaker

brainstorming

Coordinate structured brainstorming to convert vague ideas into actionable design directions.

Community
Intermediate