One-click install
npx skills add https://github.com/santanapol/agent-skills --skill spec-santanapol
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec
Source: https://github.com/santanapol/agent-skills/tree/main/.cursor/skills/spec
Command: npx skills add https://github.com/santanapol/agent-skills --skill spec-santanapol

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Starting development without clear, agreed-upon requirements leads to misaligned features, wasted coding effort, and costly rework when stakeholders find the final output does not match their expectations.

Core Features & Use Cases

  • Guided Requirement Gathering: Asks targeted clarifying questions to capture project objectives, target users, core features, tech stack constraints, and explicit project boundaries to eliminate all ambiguity.
  • Structured Spec Generation: Compiles all gathered information into a standardized SPEC.md file that covers objectives, commands, project structure, code style, testing strategy, and boundaries.
  • Use Case: When building a new customer-facing checkout flow, use this skill to first document required payment methods, fraud prevention rules, and error handling logic before writing any implementation code.

Quick Start

Use the spec skill to gather all requirements for your new user authentication feature, generate a structured SPEC.md file, save it to your project's _mission-control folder, and get stakeholder approval before starting any implementation work.

Frequently Asked Questions about spec

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

FAQPage Schema
How do I write a feature specification before starting software development?

To write a feature specification, you can use a guided requirement gathering process that asks targeted questions about project objectives, target users, and core features to eliminate ambiguity before coding begins.

What is spec-driven development and how does it prevent misaligned features?

Spec-driven development enforces structured requirement definition prior to code implementation, ensuring stakeholder alignment and eliminating misaligned features and costly rework by agreeing on specifications first.

How do I gather requirements for a new project and document tech stack constraints?

You gather requirements by answering clarifying questions about project boundaries and tech stack constraints, which are then compiled into a standardized SPEC.md file covering objectives, commands, and code style.

What should be included in a pre-development software planning document?

A pre-development software planning document should include project objectives, core features, tech stack constraints, code style guidelines, testing strategy, and explicit project boundaries for stakeholder sign-off.

When do I need to generate a structured spec file for a product change?

You need to generate a structured spec file when undertaking new feature development, project initialization, or significant product changes where clear, agreed-upon specifications are required before work begins.

Can I use structured requirement gathering for defining project boundaries and testing strategy?

Yes, structured requirement gathering captures explicit project boundaries and testing strategies, compiling them into a standardized SPEC.md file to ensure all stakeholders agree on the scope before implementation.