spec

Write and validate product feature specifications with testable requirements.

Updated Jun 24, 2026
One-click install
npx skills add https://github.com/AvatarGanymede/pcraft --skill spec-avatarganymede
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec
Source: https://github.com/AvatarGanymede/pcraft/tree/main/.agents/skills/spec
Command: npx skills add https://github.com/AvatarGanymede/pcraft --skill spec-avatarganymede

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides a structured approach to writing and validating product feature specifications, ensuring clarity and testability before development begins.

Core Features & Use Cases

  • Feature Definition: Capture the "what & why" of a product feature in a living document.
  • Testability: Ensure that a fresh agent can reimplement or test the feature based on the spec.
  • Scope Management: Determine if the topic is a feature and not a bug fix or refactor.
  • Template Guidelines: Follow a template with sections like "Why", "What", and "Scenarios" to maintain consistency.

Quick Start

Create a new spec for a feature by running the command 'spec create <feature-name>'.

Frequently Asked Questions about spec

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

FAQPage Schema
What is a product feature specification and why do I need observable behaviors?

A product feature specification captures the "what and why" of a feature in a living document. Defining observable behaviors ensures requirements are testable and clear enough for any developer to reimplement or validate the feature.

How do I write testable requirements for new product features?

To write testable requirements, use a structured template with sections for user problems, must-have behaviors, and scenarios. This ensures clarity and testability before development begins, guiding the entire implementation process.

When should I write a feature specification instead of a bug fix document?

You should write a feature specification when introducing new product capabilities, not for bug fixes or refactoring. Scope management checks ensure the topic defines new observable behaviors rather than addressing existing code defects.

How do I create a new spec for a feature using the template?

Create a new spec by running the command 'spec create <feature-name>'. This initiates a structured template containing "Why", "What", and "Scenarios" sections to maintain consistency across your product development documents.

What sections should be included in a feature definition template?

A feature definition template should include sections for user problems, must-have behaviors, and scenarios. These sections capture the feature's purpose and validate its testability by detailing specific observable behaviors.

Does a good feature specification guarantee a fresh agent can reimplement the feature?

Yes, the specification's core testability goal ensures a fresh agent can reimplement or test the feature. By focusing on observable behaviors and structured scenarios, the document provides exact validation criteria for new development.