tapcanvas-workflow-orchestrator

Generate executable TapCanvas canvas plans from live project data.

523|125|Updated Nov 11, 2025
One-click install
npx skills add https://github.com/anymouschina/TapCanvas --skill tapcanvas-workflow-orchestrator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tapcanvas-workflow-orchestrator
Source: https://github.com/anymouschina/TapCanvas/tree/main/apps/agents-cli/skills/tapcanvas-workflow-orchestrator
Command: npx skills add https://github.com/anymouschina/TapCanvas --skill tapcanvas-workflow-orchestrator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Based on live TapCanvas project status, node context, and chapter evidence, this skill generates the next-step canvas orchestration decisions, without relying on docs, assets, or ai-metadata.

Core Features & Use Cases

  • Generates executable canvas plans that drive multi-step workflows across nodes and chapters.
  • Anchors planning to real-time project data and evidence, ensuring continuity and traceability.
  • Outputs a <tapcanvas_canvas_plan> for direct ingestion by the TapCanvas engine.
  • Supports continuity-aware adjustments when node states change.

Quick Start

Provide the current project state, node context, and chapter evidence to generate the next-step TapCanvas canvas plan.

Frequently Asked Questions about tapcanvas-workflow-orchestrator

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

FAQPage Schema
How do I generate a canvas orchestration plan from live project status?

You generate a canvas orchestration plan by feeding live project status, node context, and chapter evidence into the orchestrator. It produces an executable multi-step canvas plan that ensures continuity and traceability without relying on docs, assets, or ai-metadata.

What is context-aware workflow orchestration for multi-step planning?

Context-aware workflow orchestration is the process of generating next-step decisions across nodes and chapters. It anchors multi-step planning to current project status and chapter evidence rather than static documentation to drive the workflow forward.

Can I use project docs or asset files to generate a TapCanvas canvas plan?

No, you cannot use project docs, assets, or ai-metadata to generate a TapCanvas canvas plan. The orchestration explicitly relies entirely on live project status, node context, and chapter evidence for planning.

How do I handle workflow continuity when node states change in TapCanvas?

To handle workflow continuity when node states change, apply continuity-aware adjustments to the orchestration plan. The skill uses live node context to adjust the next-step canvas plan dynamically during state transitions.

What is the best way to drive multi-step workflows across nodes and chapters?

The best way to drive multi-step workflows across nodes and chapters is to generate an executable canvas plan from live project data. This evidence-based approach ensures the workflow relies on current node context for traceable orchestration.

What format does the TapCanvas orchestrator output for direct engine ingestion?

The TapCanvas orchestrator outputs a tapcanvas_canvas_plan format for direct engine ingestion. This format contains the actionable next-step orchestration decisions derived from current project status and chapter evidence.