Provides the "how-to" for workflow / task execution orchestration. Defines methods for planning multi-phase task/workflows, implementing them through agent delegation, and managing artifacts.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Knowledge base for orchestrating multi-phase workflow executions with standardized folder structures and agent delegation.
This skill embodies seven key orchestration principles:
A core architectural principle that emerges from delegation: pass file paths, not content. This enables agents to load context when needed, maintaining high signal-to-noise ratio. Instead of inlining everything upfront, each agent reads only the files it needs for its specific task.
All task/workflow executions follow this structure:
/{base-dir}/{task/workflow-name}/{YYYY-MM-DD_HH:MM}/
├── data/ # Input files (optional)
├── artifacts/ # Phase outputs
│ ├── 01-*.md
│ ├── 02a-*.md
│ ├── 02b-*.md
│ └── 03-*.md
├── PLAN.md # Initial plan
└── RESEARCH.md/STRATEGY.md/CONTENT.md # Final output
Where base-dir is either research, strategy or content.
See Artifacts for naming conventions and folder structure details.
For one-off, custom tasks that require bespoke execution plans:
Purpose: Create a structured execution plan
Inputs:
Process: See Planning
Outputs:
Purpose: Execute the plan through agent delegation
Inputs:
Process: See Implementation
Outputs:
For repeatable, standardized workflows defined by Marketing Architects:
Purpose: Convert plain-English WORKFLOW.md into structured EXECUTE.md
Inputs:
Process: See Workflow to Execute
Outputs:
/execute commandPurpose: Run pre-defined workflow using EXECUTE.md blueprint
Inputs:
Process: See Executing
Outputs:
Purpose: Restart execution from specific phase with selective regeneration
Inputs:
Process: See Resuming
Outputs:
scripts/create_execution_folder.py - Creates timestamped execution foldersassets/PLAN_EXECUTE_template.md - Plan/Execute blueprint templateNo reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
[00] TnR ABSOLUTE RIGOR — Systemic Verification Doctrine. Forced cognitive exertion for high-stakes investigations. Mandates absolute deconstruction, mathematical proof chains, and ≥95% derived certainty. Zero-tolerance for heuristics or sentiment-based reasoning. Shortcuts are defined as intentional hallucinations.
The English summary is being prepared. Showing the original description.
Configures 2-Agent workflow between PM and implementation roles. Use when user mentions 2-Agent, 2エージェント, PM連携設定, Cursor設定, Cursor連携, 2-agent運用. Do NOT load for: 単独運用, ワークフロー実行, ハンドオフ処理.
The English summary is being prepared. Showing the original description.
Appends relevant hashtags to journal entries based on content analysis. Intended for LLM execution.
The English summary is being prepared. Showing the original description.
Add a new AI coding agent to Agent Sandbox. Creates all required files (Dockerfile, templates, CI, docs) and wires the agent into the CLI, proxy, and build system.
The English summary is being prepared. Showing the original description.
Add a new property to the AI agents database. Use when the user wants to add, create, or introduce a new column, property, field, or feature to track across all agents in the comparison matrix. Handles all four required steps - database updates, groups.json, table display, and GitHub issue templates.
The English summary is being prepared. Showing the original description.
Add new Agent templates to the meta-agent-skills framework.
The English summary is being prepared. Showing the original description.