workflow-implementation

Implements the Multica agentic workflow platform across twelve incremental pull requests.

Updated Jun 8, 2026
One-click install
npx skills add https://github.com/vovanostm-public/multica --skill workflow-implementation-vovanostm-public
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: workflow-implementation
Source: https://github.com/vovanostm-public/multica/tree/main/.agents/skills/workflow-implementation
Command: npx skills add https://github.com/vovanostm-public/multica --skill workflow-implementation-vovanostm-public

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Building a multi-stage agentic workflow platform requires coordinating runtime execution, definition versioning, evidence validation, owner resolution, action policies, and UI components without breaking existing behavior. This Skill provides a sequenced 12-PR implementation plan with architecture constraints, rollback strategies, and verification commands. ## Core Features & Use Cases - Sequenced PR Plan: Twelve incremental PRs covering runtime correctness, definition versioning, stage execution plans, evidence contracts, owner binding, action registry, pipelines, worktree environments, catalog, control panel UI, workflow studio, and self-improvement loops. - Architecture Constraints: Enforces rules such as workflow_execution as source of truth, pinned immutable definition versions, open workflow keys, and approved action registry for side effects. - Rollback and Verification: Each PR documents fallback behavior plus Go test and pnpm typecheck commands. - Use Case: A backend engineer implementing stage execution plans follows PR-02 to build the PlanBuilder with deterministic JSON snapshots and redacted agent task contracts. ## Quick Start Ask the agent to implement the next workflow platform PR following the workflow-implementation plan, starting with the runtime correctness baseline.

Frequently Asked Questions about workflow-implementation

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

FAQPage Schema
How do I implement an agentic workflow runtime in Go?▼

Start with a workflow_execution table as the runtime source of truth, then add an EnsureExecution service that creates executions and initial stage runs. Implement a Transition method that merges persisted evidence before validation and returns structured blocked reasons.

How to version workflow definitions without breaking running executions?▼

Store definitions in an immutable workflow_definition_version table with checksums, and pin running executions to a published version ID. Keep a draft definition on the workspace workflow and backfill version 1 from existing definitions.

What is a stage execution plan snapshot?▼

A StageExecutionPlan is a deterministic JSON snapshot capturing owner resolution, evidence contracts, prompt contracts, and action plans for a stage run. The full plan is stored in the stage run input snapshot while a redacted version without secrets goes to the agent task queue.

How do I validate workflow transition evidence?▼

Use a typed evidence registry with canonical namespaces and schema validators for keys like context.blackboard.v1. ValidateTransitionEvidence checks typed requirements first and falls back to legacy key-presence checks behind a feature flag.

Can existing workflows keep running during the migration?▼

Yes, each PR preserves existing behavior through fallbacks: legacy issue fields act as compatibility mirrors, old snapshot paths remain valid, and feature flags gate typed validation and pipeline modes. Down migrations drop new tables cleanly.