sayt-lifecycle

Automate lifecycle configuration across seven environments with verb-pair workflows.

1|1|Updated Apr 16, 2025
One-click install
npx skills add https://github.com/bonisoft3/iris --skill sayt-lifecycle
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sayt-lifecycle
Source: https://github.com/bonisoft3/iris/tree/main/plugins/sayt/skills/sayt
Command: npx skills add https://github.com/bonisoft3/iris --skill sayt-lifecycle

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The unified lifecycle tool helps teams automate and coordinate development workflows across environments by centralizing lifecycle tasks in sayt.

Core Features & Use Cases

  • Standardized verb-based workflow: setup/doctor, build/test, generate/lint, launch/integrate, release/verify, with a clear mapping to existing config files.
  • Reuses your current configs (.mise.toml, .vscode/tasks.json, compose.yaml, skaffold.yaml) to keep CI, IDE, and CLI in sync.
  • Use Case: A project needing repeatable lifecycle across dev, staging, and production with minimal drift.

Quick Start

Start by running sayt doctor to verify your seven environments and bootstrap the initial lifecycle configuration.

Frequently Asked Questions about sayt-lifecycle

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

FAQPage Schema
How do I keep development lifecycle workflows consistent across dev, staging, and production environments?

A seven-environment model standardizes lifecycle tasks across pkg, cli, ide, cnt, k8s, cld, and xpl. It enforces consistent setup, build, test, and deployment workflows across environments, preventing configuration drift from development to deployment.

How do I synchronize CI, IDE, and CLI configurations using my existing config files?

You can synchronize CI, IDE, and CLI configurations by reusing your existing config files like .mise.toml, .vscode/tasks.json, compose.yaml, and skaffold.yaml. Centralizing these tasks keeps all environments in sync without requiring completely new configuration setups.

What is a verb-pair workflow model for software development lifecycle automation?

A verb-pair workflow model maps lifecycle actions to standardized pairs like setup/doctor, build/test, generate/lint, launch/integrate, and release/verify. This provides clear, repeatable lifecycle guidance and maps directly to your existing project configuration files.

How do I verify my environment configuration before bootstrapping a unified lifecycle workflow?

Run a doctor command to verify your seven environments and bootstrap the initial lifecycle configuration. This checks your setup against the standardized model and ensures all required environments are correctly configured before applying the workflow.

Does this lifecycle automation tool work with Kubernetes and cloud deployment workflows?

Yes, the seven-environment model explicitly includes k8s (Kubernetes) and cld (cloud) environments. It integrates with skaffold.yaml and compose.yaml to standardize build, test, and deployment workflows across local containers and cloud infrastructure.

What is the best way to automate repeatable build and deployment tasks across multiple environments?

The best way to automate repeatable tasks is centralizing them with a standardized verb-pair workflow. By mapping build/test and release/verify actions to existing config files, teams ensure minimal drift and consistent execution across all seven environments.