specification-first

Create structured behavior specifications before implementation.

78|20|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/NoobyGains/godmode --skill specification-first
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: specification-first
Source: https://github.com/NoobyGains/godmode/tree/main/skills/specification-first
Command: npx skills add https://github.com/NoobyGains/godmode --skill specification-first

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the common failure mode of AI coding agents writing code without a clear understanding of requirements, leading to inconsistent, incorrect, or duplicated logic. It enforces a structured approach to defining system behavior before implementation.

Core Features & Use Cases

  • Mandatory Specification: Ensures that no implementation code is written without a prior, approved behavior specification.
  • Structured Specification Document: Provides a template for defining inputs, outputs, constraints, edge cases, and acceptance criteria.
  • Use Case: When building a new API endpoint, this Skill ensures a detailed specification is created and approved, covering all request parameters, response formats, error conditions, and validation rules before any code is written.

Quick Start

Use the specification-first skill to create a behavior specification for the new user authentication module.

Frequently Asked Questions about specification-first

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

FAQPage Schema
What is specification-first development for API design?▼

Specification-first development is a methodology that mandates creating a structured behavior specification defining inputs, outputs, constraints, and acceptance criteria before writing any implementation code for an API.

How do I define behavior and edge cases before writing code?▼

You define behavior by creating a structured specification document detailing inputs, outputs, constraints, edge cases, and acceptance criteria, ensuring all requirements are approved before implementation begins.

Why does my AI agent write inconsistent or duplicated logic?▼

AI agents write inconsistent logic when they write code without a clear understanding of requirements; enforcing a structured specification-first approach ensures consistent behavior by defining requirements upfront.

Can I use behavior-driven development to plan new API endpoints?▼

Yes, you can use this behavior-driven development approach to plan new API endpoints by defining request parameters, response formats, error conditions, and validation rules in a specification before coding.

What should I not use a specification-first approach for?▼

You should avoid using the specification-first approach for rapid prototyping or exploratory coding, as it mandates creating and approving a detailed behavior specification before any implementation code can be written.

Does specification-first development work with intent discovery and task planning?▼

Yes, specification-first development integrates directly with intent discovery, task planning, and test-first development skills, using the behavior specification as the authoritative artifact for software development.