spec-driven-workflow

Generate and validate specification templates before implementation code.

Updated Nov 3, 2016
One-click install
npx skills add https://github.com/xleliberty/mydotfiles --skill spec-driven-workflow-xleliberty
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-driven-workflow
Source: https://github.com/xleliberty/mydotfiles/tree/main/.config/.claude/plugins/cache/claude-code-skills/engineering-advanced-skills/2.1.2/spec-driven-workflow
Command: npx skills add https://github.com/xleliberty/mydotfiles --skill spec-driven-workflow-xleliberty

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill eliminates rework and ambiguity by enforcing a strict contract where specifications are written, validated, and approved before a single line of implementation code is generated.

Core Features & Use Cases

  • Spec Generation & Validation: Automatically generate spec templates and validate them against strict completeness criteria to ensure they are ready for implementation.
  • Test Extraction: Automatically extract test stubs from acceptance criteria to ensure TDD compliance from the start.
  • Use Case: When starting a new feature, use this Skill to define functional requirements, API contracts, and acceptance criteria, ensuring the entire engineering team is aligned before development begins.

Quick Start

Use the spec-driven-workflow skill to generate a new specification template for the user authentication feature.

Frequently Asked Questions about spec-driven-workflow

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

FAQPage Schema
How do I enforce specification-first development for complex feature planning?

Specification-first development is enforced by generating spec templates and validating them against strict completeness criteria before any implementation code is written, eliminating ambiguity and reducing software defects.

How does generating test stubs from acceptance criteria support TDD integration?

Generating test stubs from acceptance criteria supports TDD integration by automatically extracting test scaffolding from validated specifications, ensuring test-driven development compliance from the very start of implementation.

What is the best way to define API contracts and validate them before coding?

The best way to define API contracts is using a spec-first workflow that automatically generates specification templates and validates them against strict completeness criteria to ensure they are ready for implementation.

Can I use spec-driven workflows to verify non-functional requirements?

Yes, spec-driven workflows support non-functional requirement verification by ensuring specifications are validated against strict completeness criteria and measurable acceptance standards before implementation begins.

Why does specification-first development eliminate ambiguity in software engineering?

Specification-first development eliminates ambiguity by enforcing a strict contract where functional requirements and API contracts are written, validated, and approved before any implementation code is generated.

When do I need RFC 2119 compliance in my specification validation process?

RFC 2119 compliance is needed when defining strict API contracts and functional requirements for complex features, ensuring specification validation meets rigorous engineering standards and eliminates rework.