Spec Driven Workflow
Use when the user asks to write specs before code, define acceptance criteria, plan features before implementation, generate tests from specifications, or follow spec-first development practices.
Before & after
Same prompt, same agent — the only difference is the skill.
That's a good feature idea. You'll want to think about what resetting means—does the user confirm first? What data gets reset? How long does the operation take? What happens if it fails? I could help you work through the requirements. There are probably some edge cases to consider too, like what if a user's default preferences haven't been set yet. I'd suggest documenting the happy path and then thinking about error scenarios. Would you like me to outline some acceptance criteria?
FEATURE SPECIFICATION: PREFERENCES RESET REQUIREMENT Users can restore all account settings to system defaults with a single action, reverting customizations made over time without affecting data or content. ACCEPTANCE CRITERIA • User can trigger reset from Settings > Advanced > Reset all preferences • Confirmation dialog requires user to type "RESET" to proceed • Operation completes within 2 seconds • POST /api/v1/users/me/preferences/reset requires authenticated session • Returns HTTP 200 with diff object showing what changed • All 47 preference keys revert to system defaults (documented in DEFAULTS.json) • User receives email confirmation within 30 seconds • Event "preferences_reset" logged with user_id, timestamp, ip_address EDGE CASES & SOLUTIONS • User clicks reset twice: second call returns 409 "already in progress" (prevents race) • Partial failure (email fails but reset succeeds): Return 202 partial success, queue retry • User has no reset permission: Return 403 with reason (e.g., organization-managed account) • Old defaults don't exist: Use hardcoded FALLBACK_DEFAULTS, log as "system_default_missing" ROLLBACK PLAN • Preference history maintained in audit_log for 90 days • User can restore any previous state via Settings > Preference history • Undo available for 24 hours after reset
About this skill
name: spec-driven-workflow description: Use when Use when the user asks to write specs before code, define acceptance criteria, plan features before implementation, generate tests from specifications, or follow spec-first development practices.
Spec Driven Workflow
Use when the user asks to write specs before code, define acceptance criteria, plan features before implementation, generate tests from specifications, or follow spec-first development practices.
What you get
- Public GitHub repo (alirezarezvani/claude-skills)
- the spec-driven-workflow skill folder with SKILL.md. Part of a 337-skill / 30-agent / 70-command install.
Customize your output
- Fork the repo and adapt the skill's instructions and references to your workflow.
Example output
Activates automatically when your request matches Spec Driven Workflow; chains with the other skills, agents, and commands in the collection.
Best for
Creators, builders, and teams using Claude Code.
SKILL.md preview
---
name: spec-driven-workflow
description: Use this skill when the user wants to write specs before code, define acceptance criteria, plan features before implementation, or generate tests from specifications.
version: 1.0.0
category: Development / Engineering
author: AgentVolt
license: proprietary
tags:
- development
- engineering
---
# Spec Driven Workflow
Drives feature work from a written specification and acceptance criteria first, generating tests from the spec before implementation begins.
## When to use
… (sign up to view the full skill)More development skills
View all Development skills →Generate
Scaffold code, tests, and boilerplate from a short spec.
Performance Profiler
Systematic performance profiling for Node.js, Python, and Go applications.
Threat Detection
Use when hunting for threats in an environment, analyzing IOCs, or detecting behavioral anomalies in telemetry.
Agent Harness
Turns a domain folder of skills into a bounded agentic loop: compile a goal into a task plan, execute with the domain's tools, verify every task, retry within a budget.