sails-feature-workflow

Enforce a stage-by-stage workflow for implementing features in existing Gear/Vara Sails applications.

17|23|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/gear-foundation/vara-skills --skill sails-feature-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sails-feature-workflow
Source: https://github.com/gear-foundation/vara-skills/tree/main/skills/sails-feature-workflow
Command: npx skills add https://github.com/gear-foundation/vara-skills --skill sails-feature-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the common problem of builders skipping required workflow steps when implementing features in existing Gear/Vara Sails applications, which leads to broken implementations, missed guardrails, incorrect client generation, and failed test runs.

Core Features & Use Cases

  • Structured Stage-by-Stage Workflow: Enforces a mandatory sequence from spec creation and architecture planning through task decomposition, Rust implementation, IDL regeneration, gtest execution, and local smoke validation.
  • Cross-Skill Integration: Automatically routes to specialized skills for contract evolution, gstd API selection, message execution semantics, and fungible token features when those domains are relevant to the work.
  • Use Case: If you are adding a new user-facing feature to an already deployed Sails application, this Skill ensures you follow all required documentation, review, and testing steps to avoid costly rework or production issues.

Quick Start

Use the sails-feature-workflow skill to implement a new feature in your existing Gear/Vara Sails application following the required stage-by-stage process.

Frequently Asked Questions about sails-feature-workflow

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

FAQPage Schema
How do I implement a new feature in an existing Sails application on Gear or Vara?

To implement a feature in a Sails application, follow a structured workflow from spec creation and architecture planning through Rust implementation, IDL and typed client regeneration, gtest execution, and local smoke validation.

What steps are required to add a new feature to an existing Gear Sails repository?

Required steps for a Sails feature include task decomposition, Rust implementation, IDL and typed client regeneration, gtest execution, and local smoke validation, with cross-skill reviews for contract evolution and message execution semantics.

Does the Sails feature workflow support greenfield project scaffolding?

The Sails feature workflow does not support greenfield scaffolding, Vara.eth paths, etexe paths, or non-Sails repositories. It strictly applies to feature work in existing Gear/Vara Sails repositories.

Why do my Sails feature implementations fail gtest runs or generate incorrect clients?

Sails feature implementations fail when skipping required workflow steps like IDL regeneration and architecture planning. Enforcing a stage-by-stage process with explicit guardrails prevents broken implementations and incorrect client generation.

Can I use this workflow for fungible token features in my Sails app?

Yes, the Sails feature workflow automatically routes fungible token features to specialized cross-skill reviews, coordinating domain-specific checks for contract evolution, gstd API selection, and message execution semantics.

When do I need to regenerate the IDL and typed client in a Sails workflow?

You need to regenerate the IDL and typed client during the Sails feature workflow after Rust implementation, ensuring the generated client matches the updated contract before proceeding to gtest execution and local smoke validation.