specify

Convert elicitation output or PRDs into formal specifications defining what to build and why.

25|7|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/xoai/sage --skill specify-xoai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: specify
Source: https://github.com/xoai/sage/tree/main/core/capabilities/planning/specify
Command: npx skills add https://github.com/xoai/sage --skill specify-xoai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill transforms raw elicitation output or existing PRDs into clear, actionable specifications, ensuring alignment on project goals before development begins.

Core Features & Use Cases

  • Formal Specification Generation: Creates detailed specifications outlining WHAT to build and WHY, separating requirements from implementation details.
  • PRD Translation: Converts existing Product Requirement Documents (PRDs) into technical specifications, resolving open questions and mapping requirements to architecture.
  • Use Case: After a user describes a new feature, this Skill structures their needs into a formal specification document that engineers can use as a definitive guide for development.

Quick Start

Use the specify skill to create a formal specification based on the recent user requirements.

Frequently Asked Questions about specify

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

FAQPage Schema
How do I convert a PRD into a technical specification for development?

To convert a PRD into a technical specification, you structure its raw elicitation output into formal requirements defining WHAT to build and WHY. This resolves open questions and maps requirements to architecture before implementation begins.

What is the best way to structure requirements into testable specifications?

The best way to structure testable specifications is by separating requirements from implementation details. This process transforms raw feature needs into formal documents defining the project goals and architectural mapping.

When do I need to create formal specifications from elicitation output?

You need to create formal specifications from elicitation output during the initial stages of a build or architect workflow. This ensures clear alignment on project goals and testable requirements before development starts.

Can I use this specification process for an existing Product Requirement Document?

Yes, you can use this process for an existing Product Requirement Document. It translates PRDs into formal technical specifications, resolving open questions and mapping requirements to architecture for engineering teams.

How does separating requirements from implementation details help development?

Separating requirements from implementation details helps development by ensuring alignment on project goals before coding begins. It provides engineers with a definitive guide defining WHAT to build and WHY.