spec-writing

Refine EARS specifications through structured dialogue for preconditions, postconditions, edge cases, and error handling.

Updated Nov 2, 2025
One-click install
npx skills add https://github.com/3balljugglerYu/ai_coordinate --skill spec-writing-3balljuggleryu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-writing
Source: https://github.com/3balljugglerYu/ai_coordinate/tree/main/.agents/skills/spec-writing
Command: npx skills add https://github.com/3balljugglerYu/ai_coordinate --skill spec-writing-3balljuggleryu

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the process of clarifying and enhancing EARS-formatted specifications, ensuring they are comprehensive, accurate, and ready for test generation.

Core Features & Use Cases

  • Interactive Refinement: Engages in a dialogue to flesh out preconditions, postconditions, edge cases, and error handling for existing specifications.
  • Bilingual Support: Ensures specifications are maintained in both English and Japanese.
  • Use Case: A developer has a draft specification for a new API endpoint but needs to ensure all potential failure modes and required conditions are documented before writing tests. They use this skill to systematically review and improve the spec.

Quick Start

Use the spec-writing skill to refine the specifications for the AuthViewModel class.

Frequently Asked Questions about spec-writing

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

FAQPage Schema
How do I refine an EARS specification to cover edge cases and error handling?

To refine an EARS specification, you engage in a structured interactive dialogue that systematically clarifies preconditions, postconditions, edge cases, and error handling to ensure comprehensive software documentation.

How do I maintain software specifications in both English and Japanese?

You maintain bilingual software specifications by using a refinement process that simultaneously supports English and Japanese, ensuring documentation accuracy and completeness across both languages for development workflows.

What is the best way to prepare draft API specifications for test generation?

The best way to prepare draft API specifications for test generation is to systematically review and improve them by clarifying potential failure modes and required preconditions through interactive refinement.

Can I use interactive dialogue to clarify preconditions and postconditions for existing specifications?

Yes, you can use interactive dialogue to clarify preconditions and postconditions, as the refinement process guides you through a structured conversation to flesh out existing software specifications.

Does EARS specification refinement work for documenting AuthViewModel class requirements?

Yes, EARS specification refinement works for documenting AuthViewModel class requirements by guiding you through a structured dialogue to comprehensively define preconditions, postconditions, and error handling.