Idea to spec

Skill gear-foundation/vara-skills/skills/idea-to-spec

Use when a user has a new Gear or Vara feature idea, product request, or protocol change that must become an implementable spec. Do not use for deployment-only work, runtime review, or post-release observation.From its SKILL.md

Install

npx -y skills add gear-foundation/vara-skills --skill idea-to-spec

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

17 stars17 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.2 KB, as published. Nobody here has run it

Idea To Spec

Overview

Convert a rough request into a spec that is specific enough for architecture and implementation planning.

Start Here

Read ../../references/vara-domain-overview.md first.

Use ../../assets/spec-template.md as the output shape.

Write the result to docs/plans/YYYY-MM-DD-<topic>-spec.md.

Workflow

Clarify the user goal, scope, and non-goals.
Identify actors, state changes, messages, replies, and events.
Record invariants, failure paths, and edge cases that follow from Gear/Vara actor semantics.
Turn the result into explicit acceptance criteria.
Stop when the next step is architecture, not coding.

Guardrails

Treat async messaging as the default execution model.
Name recovery and retry behavior when the feature crosses actor boundaries.
Keep the spec implementation-agnostic enough that architecture still has work to do.
Do not skip invariants or acceptance criteria.