Qspec
Description
Write a spec for the described feature. Follow the Spec-Driven Development standards from the coding-standards skill. Include: - **Goal:** One sentence describing what this does and why - **Inputs / Outputs:** What goes in, what comes out, what format - **Constraints:** Performance, security, compatibility, or size requirements - **Edge Cases:** Empty inputs, nulls, concurrent calls, failure modes - **Out of Scope:** Explicit list of what this version does not handle - **Acceptance Criteria:**
Installation
Installs to ~/.claude/commands/vscarpenter-coding-standards-skill-qspec.md
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/vscarpenter/coding-standards-skill/HEAD/.claude/commands/qspec.md -o ~/.claude/commands/vscarpenter-coding-standards-skill-qspec.md Restart Claude Code, or start a new session, for it to be picked up.
Full documentation available on GitHub
View Source RepositoryRelated Skills
Spec Kit
💫 Toolkit to help you get started with Spec-Driven Development
Testing Webapp Testing
Test local web applications using Playwright for UI verification and debugging
Testing #29
, [#52](https://github.com/affaan-m/everything-claude-code/issues/52), [#103](https://github.com/affaan-m/ever
Testing Fix Issue
by metabase - Addresses GitHub issues by taking issue number as parameter, analyzing context, implementing sol
Testing Pypict Test Design
Design comprehensive test cases using PICT (Pairwise Independent Combinatorial Testing) for optimized test sui
Testing gstack
| 15,000+ | Garry Tan's exact Claude Code setup: 6 opinionated tools that serve as CEO, Eng Manager, Release M
Testing