skills.rest
pageel
pageelOFFICIAL
Explore all skills by this author →
GitHub

spec-driven-development

Enforce assumption surfacing and quality gates in the /spec workflow.

48|18|Updated Feb 4, 2026
Search Tags:#requirements#acceptance criteria#governance#assumptions#spec#quality checklist#feature template
One-click install
npx skills add https://github.com/pageel/para-workspace --skill spec-driven-development-pageel
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-driven-development
Source: https://github.com/pageel/para-workspace/tree/main/templates/common/agents/skills/spec
Command: npx skills add https://github.com/pageel/para-workspace --skill spec-driven-development-pageel

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It prevents wasted engineering effort by turning unclear requirements into a governed specification that surfaces assumptions, defines boundaries, and enables objective quality checks before implementation.

Core Features & Use Cases

  • Assumption surfacing and confirmation: Forces the agent to explicitly list assumptions and wait for user confirmation when requirements are ambiguous.
  • Gated spec lifecycle with boundaries: Establishes Always / Ask First / Never rules so scope, permissions, and prohibitions are clear.
  • Quality checklists and templates: Provides the feature-spec template and a structured checklist to validate objective success criteria and document completeness.
  • Resource router for the /spec workflow: Automatically points the agent to the correct templates and checklists for spec creation and review.

Quick Start

Use the /spec workflow to create or review a feature specification, and ensure the agent surfaces and confirms assumptions before proceeding.

Frequently Asked Questions about spec-driven-development

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

FAQPage Schema
How do I turn ambiguous requirements into testable specs?▼

To turn ambiguous requirements into testable specs, use the /spec workflow to surface assumptions, define boundaries, and establish objective acceptance criteria before implementation proceeds.

What is the best way to enforce assumption surfacing during feature specification?▼

Enforcing assumption surfacing during feature specification requires a governed lifecycle that forces the agent to explicitly list assumptions and wait for user confirmation when requirements are unclear.

How do I define scope boundaries for feature templates before coding starts?▼

Define scope boundaries by establishing Always, Ask First, and Never rules within the spec document to clarify permissions, prohibitions, and feature scope before implementation.

Can I use a quality checklist to validate acceptance criteria in a spec document?▼

Yes, you can use a structured quality checklist to validate objective success criteria and document completeness, ensuring the spec meets quality gates during the pre-implementation re-read checkpoint.

Do I need companion templates to create a governed specification?▼

Yes, creating a governed specification requires using companion templates and checklists that the resource router automatically points to for structured spec creation and review.

Related Skills

Explore More Software Engineering Skills→
kevindreekevindree

idea-refine

Refine raw ideas into actionable plans with structured thinking and markdown one-pagers.

Community
Advanced
tkstangtkstang

oat-project-spec

Formalize project discovery into a structured specification document with requirements and acceptance criteria.

Community
Advanced
Imad-OuteImad-Oute
2

mh-cto-sdlc-acceptance-test-suite

Design BDD-style acceptance test suites from user-defined criteria.

Community
Advanced
edwinhuedwinhu
19

dev-delegate

Delegate development tasks to specialized subagents with TDD and review gates.

Community
Advanced