skills.rest
tarabakz25
tarabakz25COMMUNITY
Explore all skills by this author →
Website𝕏@kz25_kmcGitHub

spec

Create, review, and implement specification documents with SPEC-NNN traceability through TDD.

1|Updated Jul 2, 2026
Search Tags:#tdd#code review#specification#requirements#traceability#sdd#spec-driven development
One-click install
npx skills add https://github.com/tarabakz25/my-skills --skill spec-tarabakz25
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec
Source: https://github.com/tarabakz25/my-skills/tree/main/spec
Command: npx skills add https://github.com/tarabakz25/my-skills --skill spec-tarabakz25

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Teams often build features from vague conversations, leading to rework, missed requirements, and code that drifts from intent. This Skill enforces spec-driven development: requirements are pinned in a written spec with traceable SPEC-NNN IDs before any code is written, and implementation is verified against those IDs. ## Core Features & Use Cases - Spec Creation (/spec create): Gathers requirements, classifies complexity (minimal/standard/full), runs a feasibility gate against external platform constraints, and saves a right-sized spec to specs/YYYYMMDD-slug.md with a Spec Items table. - Spec Review (/spec review): Delegates a 3-round structural review to isolated subagents covering completeness, contradictions, NFRs, edge cases, and feasibility, returning prioritized Critical/Major/Minor findings. - Spec Build (/spec build): Derives an implementation plan from Spec Items, enforces TDD with SPEC-NNN IDs in every test name, and runs a compliance grep to confirm no P0 requirement is unimplemented. - Use Case: Before building a payments API, run /spec create payments-api api to produce a reviewed spec, then /spec build payments-api so every test and commit traces back to a SPEC ID. ## Quick Start Ask the agent to run /spec create payment-creation to draft a new feature specification with traceable requirement IDs.

Frequently Asked Questions about spec

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

FAQPage Schema
How do I create a specification document before coding a feature?▼

Run /spec create with a kebab-case slug and optional type (feature, api, system, data). The skill gathers requirements, selects sections based on complexity tier, checks feasibility of platform-dependent requirements, and saves the spec to specs/YYYYMMDD-slug.md with a Spec Items table.

How to implement code from a written spec with traceability?▼

Run /spec build with the spec ID after the spec passes review. The skill derives an implementation plan from Spec Items, requires every test name to include its SPEC-NNN ID, and runs a grep-based compliance check to confirm no P0 requirement is left unimplemented.

What is spec-driven development and when should I use it?▼

Spec-driven development treats a written spec as the single source of truth: if it is not in the spec, do not build it. Use it for features where requirements must be pinned before coding; skip it for one-line bug fixes, exploratory spikes, or pure refactors.

Does the spec review use subagents or run inline?▼

Review is delegated to isolated subagents via the Task tool with readonly access, never run inline by the parent agent. Large or high-stakes specs can fan out to four parallel subagents, one per review perspective, with the parent synthesizing results.

When should I not use a full specification template?▼

Avoid full templates for small changes. The skill classifies specs into minimal, standard, and full tiers; a minimal spec of 50-120 lines covers single behaviors or one endpoint, and omitted sections are listed in an Excluded Sections table instead of filled with N/A placeholders.

Related Skills

Explore More Software Engineering Skills→
eai-toolseai-tools

gofer_hydrate

Reverse-engineer specifications from existing codebases into research documents.

Official
Advanced
Hubble-incHubble-inc

Implement Plan

Implement code from PLAN.md and SPEC.md using Test-Driven Development cycles.

Official
Advanced
overviewlabsoverviewlabs

requesting-code-review

Automate pre-commit verification with security scans, quality gates, and reviewer subagents.

Community
Advanced
ConsiliencyConsiliency
2

claude-plan-detailed

Writes an implementable plan for one bounded code change with verification and handoff.

Official
Advanced