exec-ears

Name: exec-ears
Availability: InStock
Author: sangilmo

Select and execute pending EARS specs with state transitions and execution results.

1|Updated Nov 14, 2024

Search Tags:#automation #workflow #testing #spec #ears #project-management #execute

Ready to run

npx skills add https://github.com/SangIlMo/.dotfiles --skill exec-ears

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: exec-ears
Source: https://github.com/SangIlMo/.dotfiles/tree/main/.claude/skills/exec-ears
Command: npx skills add https://github.com/SangIlMo/.dotfiles --skill exec-ears

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

pending EARS spec execution is streamlined by selecting and running pending specs with deterministic state transitions and post-run documentation.

Core Features & Use Cases

Identify pending specs for the current project.
If multiple specs exist, present a list and prompt user to choose.
Move selected spec from pending to doing, then implement per Requirements, Scope, and Acceptance Criteria.
Append an Execution Result with timestamp, status, Changes, and Notes, then move spec to done.
Optional tester pane automation to trigger tests after execution.

Quick Start

Ask CLAUDE to select and execute the pending EARS spec for the current project.

Frequently Asked Questions about exec-ears

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

FAQPage Schema

How do I execute pending EARS specs for a project?▼

To execute pending EARS specs, the Skill opens and evaluates your project's pending specs, prompts for selection when multiple exist, and implements per Requirements, Scope, and Acceptance Criteria. It ensures deterministic state transitions from pending to doing to done with execution results.

What is the EARS spec state transition process?▼

The EARS spec state transition process moves selected specs from pending to doing during implementation, then to done after appending an Execution Result with timestamp, status, Changes, and Notes. This enforces deterministic state management for project requirements.

Can I trigger tests automatically after running an EARS spec?▼

Yes, you can trigger tests automatically after running an EARS spec. The Skill optionally triggers a tester pane for validation immediately after executing the pending spec and appending the Execution Result to the documentation.

How are multiple pending specs selected for execution?▼

When multiple pending specs exist, the Skill presents a list of all pending specs for the current project and prompts you to choose which one to execute. It then moves the selected spec from pending to doing for implementation.

What does an EARS spec execution result include?▼

An EARS spec execution result includes a timestamp, status, Changes, and Notes appended to the spec. This documentation occurs after enforcing the Requirements, Scope, and Acceptance Criteria and moving the spec to done.