specify

Transform vague business intent into structured requirements and acceptance criteria.

Updated May 7, 2025
One-click install
npx skills add https://github.com/enchantednatures/.dotfiles --skill specify-enchantednatures
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: specify
Source: https://github.com/enchantednatures/.dotfiles/tree/main/.config/opencode/skills/specify
Command: npx skills add https://github.com/enchantednatures/.dotfiles --skill specify-enchantednatures

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Transform vague business intent into precise, actionable specifications and PRDs to guide AI-enabled development.

Core Features & Use Cases

  • Converts goals into structured requirements and acceptance criteria.
  • Produces repeatable PRDs to align engineers, designers, and stakeholders.
  • Ideal for new features, major refactors, API changes, and governance reviews.

Quick Start

Draft a one-line business goal and this skill will draft a complete PRD.

Frequently Asked Questions about specify

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

FAQPage Schema
How do I turn vague ideas into a concrete PRD?

To turn vague ideas into a concrete PRD, draft a one-line business goal to generate structured requirements, acceptance criteria, and a specification serving as a single source of truth for stakeholders.

What is a spec-first process for product management?

A spec-first process for product management uses detailed specifications and PRDs to guide implementation, ensuring engineers, designers, and stakeholders align on structured requirements before development begins.

How do I write structured requirements for an API change?

Write structured requirements for an API change by transforming the business intent into precise specifications and acceptance criteria, creating a repeatable PRD to govern the implementation.

Do I need a formal specification for a major refactor?

Yes, you need a formal specification for a major refactor to establish a single source of truth, applying structured requirements and a spec-first process to guide the implementation and governance review.

What is the best way to document product requirements for AI-enabled development?

The best way to document product requirements for AI-enabled development is generating precise, actionable PRDs that transform vague business intent into structured specifications and acceptance criteria.

Can I use a single PRD to align engineers and stakeholders?

Yes, you can use a single PRD to align engineers and stakeholders by producing repeatable documentation that specifies structured requirements and acceptance criteria for new features or governance needs.