skills.rest
MysMon
MysMonCOMMUNITY
Explore all skills by this author →
GitHub

spec-philosophy

Create formal specifications before implementation using a plan-review-implement workflow.

2|Updated Jan 16, 2026
Search Tags:#workflow#planning#specification#requirements#sdd#product-management#ambiguous-requests
One-click install
npx skills add https://github.com/MysMon/Spec-Workflow-Toolkit --skill spec-philosophy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-philosophy
Source: https://github.com/MysMon/Spec-Workflow-Toolkit/tree/main/skills/core/spec-philosophy
Command: npx skills add https://github.com/MysMon/Spec-Workflow-Toolkit --skill spec-philosophy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Specification-Driven Development (SDD) provides a disciplined approach to software development by requiring explicit specifications before any implementation begins, reducing miscommunication and rework.

Core Features & Use Cases

  • Spec-First Rule: Enforces writing a complete spec before coding to establish scope and acceptance criteria.
  • Ambiguity Handling: Triggers clarification steps (interviews, requirements summaries) when requests are vague.
  • Lifecycle Alignment: maps plan → review → implement → revise with structured outputs (specs, ADRs, testable criteria) for consistent delivery.

Quick Start

Begin by creating a formal spec for a new feature using the plan → review → implement workflow to ensure clear success criteria.

Frequently Asked Questions about spec-philosophy

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

FAQPage Schema
What is specification-driven development and why use it for software planning?▼

Specification-driven development (SDD) is a disciplined approach requiring explicit specifications before implementation begins. It reduces miscommunication and rework by enforcing a spec-first rule to establish clear scope and acceptance criteria upfront.

How do I handle ambiguous product requests during requirements gathering?▼

Handle ambiguous product requests by triggering clarification steps like user interviews and requirements summaries. SDD guides this process to ensure vague requests are fully defined before moving into the implementation phase.

What is the best way to define scope and acceptance criteria before coding?▼

The best way to define scope and acceptance criteria is using a formal spec workflow mapping plan, review, implement, and revise phases. This lifecycle alignment generates structured outputs like ADRs and testable criteria for consistent delivery.

Does SDD workflow support governance needs like user stories and non-functional requirements?▼

Yes, the SDD workflow satisfies governance needs by formally defining user stories, acceptance criteria, and non-functional requirements within the specification before the implementation phase begins.

When should I not use a strict spec-first development approach?▼

Avoid a strict spec-first approach when rapid prototyping is needed before scope definition, as SDD requires complete specifications and acceptance criteria to be established before any implementation begins.

Related Skills

Explore More Product & Management Skills→
I2olanDI2olanD

requirements-elicitation

Transform vague requirements into clear, testable specifications using elicitation techniques and documentation templates.

Community
Advanced
Kafil99Kafil99

task_decomposer

Decompose specifications into ordered atomic tasks with dependencies and acceptance criteria.

Community
Advanced
jikimejikime
5

jikime-domain-architecture

Select architecture patterns, generate directory templates, and create Architecture Decision Records.

Community
Advanced
caiohbfurtadocaiohbfurtado

brainstorming

Facilitate collaborative design and requirement specification for software features.

Community
Advanced