agent-specification

Generate structured requirements, constraints, and acceptance criteria for software projects.

Updated Jul 6, 2026
One-click install
npx skills add https://github.com/shirulot/codex-skill --skill agent-specification-shirulot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-specification
Source: https://github.com/shirulot/codex-skill/tree/main/agent-specification
Command: npx skills add https://github.com/shirulot/codex-skill --skill agent-specification-shirulot

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the complexity of the SPARC methodology's Specification phase by providing a structured framework for defining requirements, constraints, and acceptance criteria, ensuring consistency and testability in project documentation.

Core Features & Use Cases

  • Requirements Structuring: Automatically generates functional and non-functional requirement templates.
  • Constraint & Use Case Mapping: Provides a standardized format for documenting technical, business, and regulatory constraints alongside detailed user flows.
  • Validation & Deliverables: Includes a built-in checklist and templates for System Requirements Specifications (SRS), data models, and OpenAPI definitions.

Quick Start

Invoke the agent-specification skill to begin the requirements analysis process for your current project task.

Frequently Asked Questions about agent-specification

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

FAQPage Schema
How do I generate structured requirements for software projects?

To generate structured requirements for software projects, invoke the agent-specification skill to automatically produce functional and non-functional requirement templates, ensuring all project documentation remains consistent and testable.

What is the SPARC specification phase and how does it work?

The SPARC specification phase defines structured requirements, constraints, and acceptance criteria for software projects, working by generating standardized templates for functional specifications, data models, and API documentation to align with stakeholder expectations.

How do I document technical and business constraints alongside user flows?

Document technical and business constraints alongside user flows by using a standardized format that maps detailed constraints directly to specific use cases, ensuring all project requirements are testable and aligned with stakeholder expectations.

Can I create OpenAPI definitions and System Requirements Specifications automatically?

Yes, you can create OpenAPI definitions and System Requirements Specifications automatically by invoking the skill, which includes built-in templates and validation checklists to generate these deliverables for your software architecture.

What's the best way to ensure project requirements are testable and documented?

The best way to ensure project requirements are testable and documented is to apply a structured SPARC specification framework that uses a built-in validation checklist and standardized templates for all functional specifications.

Do I need prior architecture documentation to start requirements analysis?

No, you do not need prior architecture documentation to start requirements analysis, as the skill provides standardized templates to generate functional specifications, data models, and constraints from your current project task directly.