You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
**Domain**: [Your domain, e.g., "API Testing"]
**Problem**: [What's repetitive/manual today?]
**SDS or SDD?**: [Do you need specs, implementation, or both?]
**Vision**: [What would your ideal speckit do?]
**Example**: [One concrete command or workflow]
Example Ideas to Inspire You
💡 SD-API-Testing (SDS + SDD)
Domain: API Testing Problem: Writing similar test cases for every endpoint, managing test data Approach:
SDS: Define API testing specifications (endpoints, test scenarios, assertions)
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
MetaSpec enables you to generate Spec-Driven X toolkits for ANY domain. We want to hear YOUR ideas!
🌟 The Spec-Driven Philosophy
Spec-Driven means: Define structured specifications → Validate & generate → Execute workflows
This pattern works for ANY domain:
🎯 Real Example: MetaSpec Uses SDS + SDD
MetaSpec itself was built using both SDS and SDD!
📐 Phase 1: SDS (Spec-Driven Specification)
Purpose: Define what a "speckit" is
Result: Clear specifications for "what is a speckit" and "what can it do"
🔧 Phase 2: SDD (Spec-Driven Development)
Purpose: Build MetaSpec toolkit itself
Result: MetaSpec CLI tool (
metaspec init,metaspec search, etc.)🚀 The Power of Composition
MetaSpec proves you can combine SDS + SDD:
🤔 Share Your Vision
What toolkit would solve YOUR pain points?
Template to get started:
Example Ideas to Inspire You
💡 SD-API-Testing (SDS + SDD)
Domain: API Testing
Problem: Writing similar test cases for every endpoint, managing test data
Approach:
Example:
metaspec init api-testing-speckit # Use SDS to define test specs, SDD to build test runner api-testing-speckit validate openapi.yaml --generate-tests💡 SD-Database-Migration (SDS only)
Domain: Database Schema Evolution
Problem: Manual migration scripts, inconsistent validation
Approach:
Example:
db-migration-speckit plan schema.yaml --check-breaking-changes💡 SD-Kubernetes-Config (SDS + SDD)
Domain: K8s Configuration Management
Problem: YAML hell, no validation, hard to reuse patterns
Approach:
Example:
k8s-speckit generate microservice.spec --output deploy/🧩 When to Use SDS vs SDD?
Most powerful: Use both (like MetaSpec itself!)
🚀 What Happens Next?
Drop your ideas below! Let's discover the next killer speckit together 🎯
Resources:
Beta Was this translation helpful? Give feedback.
All reactions