asc-workflow

Define, validate, and run multi-step workflows from .asc/workflow.json.

127|8|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/hanamizuki/solopreneur --skill asc-workflow-hanamizuki
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: asc-workflow
Source: https://github.com/hanamizuki/solopreneur/tree/main/plugins/ios-dev/skills/asc-workflow
Command: npx skills add https://github.com/hanamizuki/solopreneur --skill asc-workflow-hanamizuki

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Define, validate, and run repo-local multi-step automations with asc workflow and .asc/workflow.json. This enables reproducible automation inside a single repository, improving consistency between local development and CI.

Core Features & Use Cases

  • Define and manage workflows in the .asc/workflow.json file, enabling version-controlled automation.
  • Validate workflow structure, references, and run workflows with preview/dry-run options and nested sub-workflows, including support for private helpers.
  • Use cases include migrating from lane tools, wiring CI pipelines within a project, and orchestrating repeatable release flows that combine multiple steps and hooks.

Quick Start

Define a workflow in .asc/workflow.json and run it with asc workflow run <name>.

Frequently Asked Questions about asc-workflow

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

FAQPage Schema
How do I define and run repo-local multi-step automations for CI pipelines?

Repo-local multi-step automations are defined in an .asc/workflow.json file and executed using the asc workflow command. This enables reproducible automation inside a single repository, ensuring consistency between local development and CI environments.

Can I use nested sub-workflows and conditionals in a shell release flow?

Nested sub-workflows and conditionals are fully supported in shell release flows. The schema allows private helpers and structured hooks with top-level keys like before_all, after_all, and error, producing deterministic execution output.

What is the best way to migrate from lane tools to version-controlled CI workflows?

Migrating from lane tools to version-controlled CI workflows involves defining your steps in .asc/workflow.json. This approach replaces fragmented lane scripts with a validated, structured schema that orchestrates repeatable release flows locally and in CI.

Does asc workflow support dry-run validation for automation scripts?

Dry-run validation is supported for automation scripts, allowing you to preview workflow execution safely. The command validates the workflow structure, references, and schema before running, ensuring deterministic execution without side effects.

How do I configure environment variables and hooks for shell automation tasks?

Environment variables and hooks for shell automation tasks are configured using the top-level env and lifecycle keys like before_all in the .asc/workflow.json schema. This structure enforces validation and produces structured output for deterministic execution.