spec-first

Name: spec-first
Availability: InStock
Author: sobhan

Generate and review a specification document before coding begins.

1|Updated May 12, 2026

Search Tags:#feature development #specification #agile #scope management #stakeholder agreement

Ready to run

npx skills add https://github.com/sobhanashine/nazarato --skill spec-first-sobhanashine

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-first
Source: https://github.com/sobhanashine/nazarato/tree/main/.agents/skills/spec-first
Command: npx skills add https://github.com/sobhanashine/nazarato --skill spec-first-sobhanashine

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps prevent scope creep and ensures all stakeholders agree on the scope of a new feature before development begins.

Core Features & Use Cases

Spec Creation: Forces the creation of a short, detailed spec document for each new feature.
Stakeholder Agreement: Ensures that all relevant parties have reviewed and agreed upon the spec before code is written.
Use Case: Use this Skill when starting a new feature or task. Create a spec that includes the problem, user action, data changes, and failure modes, then get explicit sign-off before writing any code.

Quick Start

Generate a spec for a new feature by using the 'spec-first' skill and follow the four questions outlined in the documentation.

Frequently Asked Questions about spec-first

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

FAQPage Schema

How do I prevent scope creep when starting new feature development?▼

Preventing scope creep requires creating a documented specification before coding begins. This approach aligns stakeholders on project requirements, ensuring all parties review and explicitly agree on the feature scope before implementation starts.

What should be included in a software feature specification document?▼

A feature specification document should include the problem, user action, data changes, and failure modes. Generating this detailed spec ensures stakeholders agree on requirements before any code is written.

How do I get stakeholder agreement before writing code for a new feature?▼

Getting stakeholder agreement involves creating a short spec document outlining the feature scope and securing explicit sign-off. You must generate and review the specification before proceeding with implementation.

When do I need to create a specification document for agile feature development?▼

You need to create a specification document whenever starting a new feature or task in agile development. Generating a spec first ensures documented requirements exist before coding begins.

What is the best way to manage feature scope in software engineering?▼

The best way to manage feature scope is enforcing a spec-first workflow that mandates a one-page specification before coding. This prevents undocumented requirements and aligns stakeholders on the project scope.

Can I write code before the feature specification is reviewed and agreed upon?▼

No, you cannot write code before the specification is agreed upon. This approach requires generating and reviewing a spec document, securing explicit stakeholder sign-off, and only then proceeding with implementation.