goca-se

Spec Dc — Testing skill for Claude Code

Testing community

Author a behavior specification (the WHAT) — step 1 of spec → plan → execute.

How to install Spec Dc

Installs to ~/.claude/commands/goca-se-dotcontext-spec-dc.md

Terminal
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/goca-se/dotcontext/HEAD/.claude/commands/spec-dc.md -o ~/.claude/commands/goca-se-dotcontext-spec-dc.md

Restart Claude Code, or start a new session, for it to be picked up.

What Spec Dc does


description: Author a behavior specification (the WHAT) — step 1 of spec → plan → execute. argument-hint: "[feature description]"

Spec (spec-dc)

Produce a complete **behavior specification** for the feature described in $ARGUMENTS. The goal is to describe **WHAT** the system must do — precisely enough that another developer can implement and test it without asking follow-up questions — and **never HOW** to build it.

This is **step 1 of three**: `/spec-dc` (the WHAT) → `/plan-dc` (the

Alternatives in Testing

  • Flow Spec — NLSpec authoring — use when you need a structured specification from multi-AI research and consensus 2.8k ★
  • Agent Plugins Spec — Agent Plugins Specification v1.0.0 — A minimal standard for packaging agent extensions into distributable plug 1.2k ★
  • Generic Browser Test — Execute browser UI testing workflows from a plan file against any URL 363 ★

Full documentation available on GitHub

View Source Repository