spec-driven-development

Writes structured specifications covering requirements, data models, APIs, and testing before implementation.

Updated May 27, 2026
One-click install
npx skills add https://github.com/Rkaaaa404/cyberhack-SYDT --skill spec-driven-development-rkaaaa404
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-driven-development
Source: https://github.com/Rkaaaa404/cyberhack-SYDT/tree/main/.agents/skills/spec-driven-development
Command: npx skills add https://github.com/Rkaaaa404/cyberhack-SYDT --skill spec-driven-development-rkaaaa404

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Starting implementation without clear requirements leads to scope creep, rework, and misaligned expectations. This Skill enforces a specification-first workflow so every feature has a written contract covering objectives, requirements, data models, and testing before any code is written. ## Core Features & Use Cases - Spec Template: Provides a complete Markdown template with sections for objectives, must-have/nice-to-have/out-of-scope requirements, data model, API design, UI design, testing strategy, and phased implementation plan. - DaaS-Aware Guidance: Includes platform-specific considerations for DaaS collections, RBAC permissions, workflow states, scoping, and Buildpad component installation as an explicit Phase 0 step. - Review Checklist: Ships a verification checklist and red-flag list to validate specs before implementation begins. - Use Case: When asked to build a new inventory management feature, use this Skill to first produce a reviewed specification defining the data model, API endpoints, and boundaries, then implement against it. ## Quick Start Ask the AI to write a specification for your new feature using the spec-driven-development approach before writing any code.

Frequently Asked Questions about spec-driven-development

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

FAQPage Schema
How do I write a software specification before coding?▼

Use a spec template covering objective, must-have and nice-to-have requirements, out-of-scope items, data model, API design, UI design, testing strategy, and a phased implementation plan. Review the spec with stakeholders before implementing, then verify each requirement checkbox during development.

What should a feature specification document include?▼

A feature specification should include a measurable objective, specific testable requirements, explicit out-of-scope items, a data model with fields and relationships, an API endpoint table, UI component choices, a testing strategy, and boundaries defining what to always do, ask first about, and never do.

When should I skip writing a spec?▼

Skip the spec for single-file bug fixes, small refactors, or changes where the spec would be longer than the code itself. Specs add value when requirements are complex, ambiguous, or multiple people will work on the implementation.

How does spec-driven development work with DaaS platforms?▼

For DaaS applications, spec the collection and field schema instead of raw SQL, only custom endpoints since CRUD is automatic, the RBAC permission model, workflow states if content lifecycle is needed, and scope hierarchy for multi-tenant apps. Check built-in features like audit trails and versioning before speccing custom solutions.

Why do specs fail to prevent scope creep?▼

Specs fail when the out-of-scope section is empty, requirements are not testable, or the spec only covers the happy path without error cases. An explicit out-of-scope list and stakeholder review before implementation are the main defenses against scope creep.