Converts task descriptions into human-approved Gherkin acceptance specs before implementation.
npx skills add https://github.com/arayaroma/ether --skill specifier-job-arayaroma
Please help me install this Agent Skill. Skill: specifier-job Source: https://github.com/arayaroma/ether/tree/main/skills/specifier-job Command: npx skills add https://github.com/arayaroma/ether --skill specifier-job-arayaroma
specifier jobs from the ether-pro job store and processes each one against its target repository. - Spec drafting: Reads the target repo's own conventions (CLAUDE.md, AGENTS.md, existing spec directories) and writes a Gherkin .feature file covering golden-path and edge-case scenarios. - Mandatory approval gate: Never hands off a spec without explicit human approval, regardless of the autonomy tier, preventing wasted downstream implementation runs. - Automatic handoff: On approval, enqueues a pr-author job referencing the approved spec and records the run outcome for the autonomy state machine. - Use Case: You queue a job with the task "add password reset via email". The Skill drafts Given/When/Then scenarios for the reset flow, you review and approve them, and a pr-author-job is automatically created to implement exactly that spec. ## Quick Start Run the specifier job to drain pending specifier jobs and turn each task into an approved Gherkin spec before any code is written.High-intent search queries and answers about installing and using this skill.
Add a specifier job with `ether job add --type specifier --target <repo> --params '{"task":"<description>"}'`, then run this Skill. It drafts a Gherkin .feature file with Given/When/Then scenarios, waits for your approval, and hands the spec to a pr-author job.
Use `/loop <interval> /specifier-job` in a live session. Unattended CronCreate scheduling is discouraged because the mandatory human approval gate in step 4 requires someone to be present to approve each drafted spec.
No, it only produces an approved spec and never implements. On approval it automatically enqueues a pr-author job with the spec path, and that separate job handles implementation with its own scoping and TDD steps.
No. Unlike other jobs whose write actions can auto-promote to skip confirmation, the specifier approval gate always requires explicit human approval regardless of tier, because a wrong spec silently accepted wastes an entire downstream implementation run.
Running `ether job` subcommands from inside the target repo is a hard rule violation shared with other job skills. All job management commands must run from ether-pro's own directory, while only the spec file itself is written into the target repo.
neoaliensonGenerate personalized cover letters as PDFs from job descriptions and resumes.
duthahoCoordinate feature development from spec through test-first implementation and review.
mattjeffersonAnalyzes repositories to produce a research brief of structure, documentation, and patterns.
autonomy-cloudConvert user requests into template-driven task queues with priority and status tracking.