gear-foundation/idea-to-spec
skills/idea-to-spec/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add gear-foundation/vara-skills idea-to-specInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 13, 2026, 2:38 AM134.8s3 files scanned
SKILL.md
- name:
- idea-to-spec
- description:
- 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.
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.
Related Skills
gear-foundation/sails-ethexe-implementer
development
VerifiedTrustedCommunity
Use when approved tasks require Rust code changes in a Sails ethexe workspace with the ethexe feature enabled. Do not use for standard Gear/Vara Sails apps without ethexe, or when the spec or architecture is still unsettled.
17SKILL.mdUpdated May 23, 2026
gear-foundation/sails-ethexe-architecture
development
VerifiedTrustedCommunity
Use when a builder needs to design or review architecture for a Sails ethexe app with dual-transport, payable methods, Solidity interface generation, or Ethereum-style events. Do not use for standard Gear/Vara Sails apps without ethexe.
17SKILL.mdUpdated May 23, 2026
gear-foundation/gear-builtin-actors
development
VerifiedTrustedCommunity
Use when a builder needs to design or debug calls from a standard Gear/Vara Sails program into runtime builtin actors such as BLS12-381, staking, proxy, or ETH bridge, including ActorId derivation, request encoding, reply decoding, and gas or ED budgeting. Do not use for regular program-to-program messaging, Vara.eth or ethexe-only work, non-Sails repositories, or runtime-maintenance tasks inside the Gear repo.
17SKILL.mdUpdated May 16, 2026
gear-foundation/sails-indexer
development
VerifiedTrustedCommunity
Use when a builder needs a read-side indexer and query API for a standard Gear/Vara Sails app using program events, IDL-driven decoding, projected read models, and optional on-chain query enrichment. Do not use for command-side backends, generic Node APIs, non-Sails repositories, Vara.eth or ethexe-first work.
17SKILL.mdUpdated May 13, 2026