spec

Draft technical specifications covering requirements, design, APIs, and testing criteria.

1|Updated Feb 13, 2026

Search Tags:#design #testing #architecture #documentation #requirements #specifications

Ready to run

npx skills add https://github.com/aronpc/ai --skill spec-aronpc

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec
Source: https://github.com/aronpc/ai/tree/main/skills/spec
Command: npx skills add https://github.com/aronpc/ai --skill spec-aronpc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured approach to composing comprehensive technical specifications, including requirements, design, APIs, and tests, ensuring clear communication and alignment across stakeholders.

Core Features & Use Cases

Requirements gathering: Define functional and non-functional requirements with acceptance criteria.
Technical design: Outline architecture, data models, API contracts, and UI/UX considerations.
Verification & testing: Include testing strategy and milestones to validate requirements.
Use Case: When planning a new feature, generate a complete spec doc to feed implementation, reviews, and QA.

Quick Start

Create a new spec.md and fill in problem, goals, architecture, requirements, design, and tests.

Frequently Asked Questions about spec

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

FAQPage Schema

How do I write technical specifications for cross-functional feature planning?▼

To write technical specifications, define the problem statement, functional and non-functional requirements, architectural design, API contracts, and testing criteria to ensure alignment across product, design, and engineering teams.

What should be included in a technical spec document for API contracts and architecture?▼

A technical spec document should include problem statements, design decisions, data models, API contracts, UI/UX considerations, acceptance criteria, risk assessment, and open questions for comprehensive feature planning.

How do I structure requirements gathering and QA planning for a new software feature?▼

Structure requirements gathering by defining functional and non-functional requirements with acceptance criteria, then outline a verification and testing strategy including milestones to validate those requirements for QA planning.

Can I use this approach to define both functional and non-functional requirements with acceptance criteria?▼

Yes, this approach specifically supports defining both functional and non-functional requirements, establishing clear acceptance criteria, and documenting constraints to guide implementation and reviews.

What is the best way to document design decisions and testing criteria for engineering teams?▼

The best way to document design decisions is creating a structured spec file that captures architecture, API contracts, testing strategy, and milestones, ensuring clear communication across stakeholders.