skills.rest
thegeronimo
thegeronimoCOMMUNITY
Explore all skills by this author →
𝕏@RyskyGeronimoGitHub

spec-writer

Clarify scope, non-goals, acceptance criteria, and validation commands for multi-agent tickets.

44|8|Updated Jul 14, 2025
Search Tags:#planning#multi-agent#scope#ticket#acceptance-criteria#spec-writing#execplan
One-click install
npx skills add https://github.com/thegeronimo/hyperopen --skill spec-writer-thegeronimo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-writer
Source: https://github.com/thegeronimo/hyperopen/tree/main/.agents/skills/spec-writer
Command: npx skills add https://github.com/thegeronimo/hyperopen --skill spec-writer-thegeronimo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The spec_writer helps teams create or refresh the active ExecPlan for multi-agent tickets, clarifying scope, non-goals, acceptance criteria, and validation steps, and preventing production-code edits or standalone prose cleanup.

Core Features & Use Cases

  • Create or refresh the active ExecPlan for a ticket.
  • Define scope, non-goals, acceptance criteria, touched areas, and validation commands.
  • Emit structured spec data for the manager to review and approve.

Quick Start

Summon the spec_writer to draft or refresh the active ExecPlan for the current ticket.

Frequently Asked Questions about spec-writer

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

FAQPage Schema
How do I write acceptance criteria and scope for multi-agent tickets?▼

To write acceptance criteria for multi-agent tickets, you can use a spec writer to clarify scope, non-goals, validation steps, and emit structured spec data for manager review and approval.

What is an ExecPlan and when do I need to refresh it for ticket management?▼

An ExecPlan defines scope, non-goals, and validation commands for tickets. You need to refresh it when creating or updating multi-agent tasks to ensure consistent spec generation across agents and managers.

How do I generate structured spec data for a manager to review?▼

Generate structured spec data by drafting or refreshing the active ExecPlan, which outputs a structured spec payload to the multi-agent temp directory for the manager to review and approve.

Can I use spec writing to prevent production-code edits during ticket planning?▼

Yes, clarifying scope, non-goals, and acceptance criteria during ticket planning explicitly prevents production-code edits and standalone prose cleanup, keeping agents focused on defined validation steps.

Where are updated ExecPlans and spec payloads saved when defining ticket criteria?▼

Updated active ExecPlans are written to the active exec-plans directory, and the structured spec payload is output to the multi-agent tmp directory to enable consistent cross-agent spec generation.

Does multi-agent ticket spec writing require standalone prose cleanup?▼

No, multi-agent ticket spec writing does not require standalone prose cleanup. The process focuses strictly on defining scope, non-goals, and validation commands to prevent unnecessary edits.

Related Skills

Explore More Product & Management Skills→
GrinRusGrinRus
5

status

Generate a ticket status snapshot from index data, artifacts, and recent events.

Community
Intermediate
thegeronimothegeronimo
44

acceptance-tests

Designescribes acceptance and integration test proposals from frozen specs or ExecPlans for downstream teams.

Community
Intermediate
thegeronimothegeronimo
44

feature-flow

Coordinates Hyperopen feature changes via ExecPlan generation, test scaffolding, and reviewer handoffs.

Community
Advanced
YeaChan05YeaChan05

spec

Define problem, scope, and acceptance criteria into a /plan artifact.

Community
Intermediate