skills.rest
easttxkravmaga
easttxkravmagaCOMMUNITY
Explore all skills by this author →
GitHub

etkm-workflow-registry

Centralize ETKM workflow status, dependencies, and access controls.

Updated Feb 20, 2026
Search Tags:#workflow#governance#coordination#handoff#registry#process#etkm
One-click install
npx skills add https://github.com/easttxkravmaga/Claude --skill etkm-workflow-registry
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: etkm-workflow-registry
Source: https://github.com/easttxkravmaga/Claude/tree/main/skills/etkm-workflow-registry
Command: npx skills add https://github.com/easttxkravmaga/Claude --skill etkm-workflow-registry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The ETKM Workflow Registry centralizes the lifecycle and coordination of all ETKM workflows, preventing duplicate work, enforcing role boundaries, and synchronizing handoffs between Claude and Manus across the ETKM stack.

Core Features & Use Cases

  • Centralized status tracking and visibility for all workflows, with standardized statuses (PLANNED, DRAFT, APPROVED, LOADED, LIVE, PAUSED, DEPRECATED).
  • Clear role division and handoff protocols to govern copy, automation, approvals, and status updates.
  • Session-opening guidance and dependency reference workflow to ensure every session starts from a single source of truth.

Quick Start

Open the registry skill, confirm it is active, and review the live workflow registry before starting any ETKM build session.

Frequently Asked Questions about etkm-workflow-registry

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

FAQPage Schema
How do I prevent workflow duplication when coordinating tasks between multiple AI agents?▼

Preventing workflow duplication across AI agents requires a centralized registry that tracks statuses, enforces role boundaries, and synchronizes handoffs to maintain a single source of truth.

How does a centralized registry manage workflow status transitions and dependencies?▼

A centralized registry manages workflow status transitions by enforcing standardized statuses like PLANNED, LIVE, and DEPRECATED, while applying dependency tracking checks during session openings and agent handoffs.

What is the best way to govern process handoffs between Claude and Manus to avoid miscommunication?▼

Governing process handoffs between Claude and Manus requires clear role division and standardized protocols enforced by a shared registry, ensuring synchronized status updates and preventing miscommunication.

When do I need a centralized workflow registry for process coordination?▼

A centralized workflow registry is needed when managing complex process lifecycles that require access controls, dependency tracking, and synchronized handoffs across multiple agents to prevent duplicate work.

Do I need to review the registry before starting a new build session?▼

Reviewing the live workflow registry before starting a build session is required to confirm the registry is active and ensure every session operates from a single source of truth.

Related Skills

Explore More Product & Management Skills→
8Dionysus8Dionysus
4

aoa-source-of-truth-check

Identify and resolve documentation ambiguity to establish a single source of truth.

Community
Intermediate
sean-sunagakusean-sunagaku
35

team-implement

Coordinate an Agent Team to execute Wave-based plan tasks with build and test verification.

Community
Advanced
cornmanwtfcornmanwtf

access-control-matrix

Design RBAC and ABAC policies with permission boundaries and validation steps.

Community
Advanced
zerobias-orgzerobias-org

manage-localmemory

Stores and retrieves JSON phase outputs in a hidden .localmemory directory without git-tracking.

Official
Intermediate