Specs
- Specification by example / BDD / ATDD — turning requirements into concrete Given/When/Then scenarios that double as acceptance tests, driven outside-in. Language-agnostic. Use when turning a feature, user story, or vague requirement into testable behavior before coding, or clarifying acceptance criteria. Triggers: specification by example, acceptance criteria, ATDD, BDD, given when then, gherkin, outside-in.
Works with: Claude Code (native) · Cursor, Codex CLI (manual)
native: this artifact type is that client's own format
Install (Claude Code):
cp -r specs ~/.claude/skills/- Adoption: 1 repos
- Upkeep: 100.0
- Freshness: 99.0
- Evidence coverage: 84% of the inputs this score can use — the rest are unknown, and the score is discounted for it
- Health: active
- Contributors: 4
Security audit
Not scanned yet. We audit npm-published capabilities for known advisories, install-time scripts and permission surface; this one has no npm package we can resolve, or has not reached the queue.
source ↗ · skill:gurinderu/specs
Already running this? npx tashan-cli doctor checks your whole config against the Index — how it works ›
Measured 2026-08-09 · scorer s5 · how · something wrong here?