skills.rest
pomazanbohdan
pomazanbohdanCOMMUNITY
Explore all skills by this author →
GitHub

vida-runtime-development

Organize VIDA runtime work into an evidence-first TaskFlow/DocFlow workflow.

16|Updated Mar 6, 2026
Search Tags:#runtime#orchestration#evidence#runbook#taskflow#vida#docflow
One-click install
npx skills add https://github.com/pomazanbohdan/vida-stack --skill vida-runtime-development
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: vida-runtime-development
Source: https://github.com/pomazanbohdan/vida-stack/tree/main/.agents/skills/vida-runtime-development
Command: npx skills add https://github.com/pomazanbohdan/vida-stack --skill vida-runtime-development

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

VIDA runtime development often involves scattered evidence, fragmented runbooks, and complex state across TaskFlow, DocFlow, and runtime diagnostics. This skill consolidates the workflow into an evidence-first protocol to streamline investigation, documentation, and proof-closure during VIDA runtime work.

Core Features & Use Cases

  • Centralized runtime workflow for VIDA TaskFlow/DocFlow activities, including runbook references and session-scoped evidence.
  • Guided state management for active bounded units, task graphs, and parity checks between status and doctor.
  • Use Case: when diagnosing runtime defects, operators follow a structured runbook-backed process to collect evidence, mutation steps, and closure proof.

Quick Start

Begin a VIDA orchestrator session for the current epic and start recording runbook-backed runtime evidence.

Frequently Asked Questions about vida-runtime-development

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

FAQPage Schema
How do I organize VIDA runtime diagnostics into an evidence-first workflow?▼

VIDA runtime diagnostics are organized into an evidence-first TaskFlow/DocFlow workflow that structures runbook-guided task execution, captures verifiable state, and records mutation steps. This consolidates fragmented runbooks into a single protocol.

What is the best way to manage active bounded-unit state across TaskFlow and DocFlow sessions?▼

Managing active bounded-unit state across TaskFlow and DocFlow sessions requires a centralized runtime workflow that tracks task graphs, references the session-runtime-runbook, and performs status/doctor parity checks for verifiable closure.

How do I record verifiable proof-closure during orchestrator session runtime work?▼

Verifiable proof-closure during orchestrator session runtime work is recorded by collecting runbook-backed runtime evidence, tracking mutation steps, and validating status/doctor parity checks within a structured TaskFlow/DocFlow workflow.

Can I use a runbook-guided process to diagnose VIDA runtime defects?▼

A runbook-guided process can be used to diagnose VIDA runtime defects by following a structured workflow that collects evidence, records mutation steps, and captures closure proof across TaskFlow, DocFlow, and orchestrator sessions.

Why does my VIDA runtime workflow lose evidence across TaskFlow and DocFlow activities?▼

VIDA runtime workflows lose evidence across TaskFlow and DocFlow activities when state is fragmented without an evidence-first protocol. Consolidating diagnostics, session management, and runbook references into a single workflow prevents scattered records.

Related Skills

Explore More Software Engineering Skills→
KorytoKoryto
3

init

Initialize a dotagent session by claiming session state with a valid session_id.

Community
Intermediate
AesopScottAesopScott

evidence-connectors

Integrate validation connectors and link schemas into the Evidence harness.

Community
Advanced
kkyyds-hubkkyyds-hub
3

write-v5-runtime-backend

Implement V5 backend features in the runtime/orchestrator module.

Community
Advanced
terencefanterencefan
1

runbook-executor

Execute runbook workflow steps and capture signed evidence records.

Community
Advanced