specify

Guide structured implementation specification creation with acceptance criteria and approval gates.

1|Updated May 13, 2026

Search Tags:#workflow #planning #specification #requirements #delivery #agent-assisted

Ready to run

npx skills add https://github.com/Amirault/DevGate --skill specify-amirault

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: specify
Source: https://github.com/Amirault/DevGate/tree/main/.agents/skills/specify
Command: npx skills add https://github.com/Amirault/DevGate --skill specify-amirault

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This skill eliminates ambiguity and scope creep in software development by enforcing a rigorous, spec-driven workflow that ensures every feature is fully understood, stress-tested, and approved before a single line of production code is written.

Core Features & Use Cases

Structured Specification: Guides the creation of implementation specs with clear acceptance criteria and behavioral examples.
Stress-Testing: Integrates mandatory grilling sessions to probe edge cases and risks before implementation begins.
Traceability: Automatically binds conversation history to spec files, ensuring that decisions made during the design phase are preserved for the implementation and review phases.

Quick Start

Type /specify to begin the structured process of defining and refining a new implementation specification.

Frequently Asked Questions about specify

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

FAQPage Schema

How do I create an implementation specification to prevent scope creep in software development?▼

To create an implementation specification that prevents scope creep, use a structured workflow to guide codebase exploration, define acceptance criteria, and enforce an approval gate before coding begins.

What is the best way to stress-test software requirements before writing production code?▼

The best way to stress-test software requirements is to run mandatory grilling sessions that probe edge cases and assess risks, ensuring every feature is fully understood before implementation.

How do I maintain traceability between design decisions and implementation planning?▼

You can maintain traceability by binding conversation history to specification files, which preserves design decisions for the implementation and review phases.

Can I define acceptance criteria and behavioral examples for agent-assisted delivery workflows?▼

Yes, you can define acceptance criteria and behavioral examples for agent-assisted delivery workflows using a structured specification process that includes an implementation planning phase.

Does a spec-driven workflow require an approval gate before starting implementation?▼

Yes, a spec-driven workflow enforces a mandatory approval gate and implementation planning phase to maintain high quality and project readiness before development proceeds.