skills.rest
Leonardo-Corte
Leonardo-CorteCOMMUNITY
Explore all skills by this author →
𝕏@Leonardo_go_UpGitHub

maestro-v2-migration

Migrate maestroCLI code from v1 to v2 semantics.

1|Updated May 26, 2026
Search Tags:#debugging#migration#MCP tools#maestrocli#task lifecycle#memory adapter#pre-agent hook
One-click install
npx skills add https://github.com/Leonardo-Corte/local-social-smm-agent --skill maestro-v2-migration-leonardo-corte
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: maestro-v2-migration
Source: https://github.com/Leonardo-Corte/local-social-smm-agent/tree/main/reference/github-agent-orchestration/maestro/.claude/skills/maestro-v2-migration
Command: npx skills add https://github.com/Leonardo-Corte/local-social-smm-agent --skill maestro-v2-migration-leonardo-corte

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates confusion and wasted time when updating code to maestroCLI’s v2 architecture by clearly mapping legacy concepts and lifecycle behavior to the current v2 model.

Core Features & Use Cases

  • Context-to-Memory migration: Convert v1 “context” terminology and imports to v2 “memory” equivalents, including adapter and filesystem path expectations.
  • 4-state task lifecycle guidance: Correctly interpret and update task state handling to use only open, claimed, done, and blocked transitions.
  • v2 execution and backend model updates: Adapt to the removal of the v1 execution layer and the default plain-file task backend (fs), while keeping code aligned to the TaskPort interface.
  • Pre-agent hook and research-phase behavior: Understand how pre-agent injects task specs and how tool detection occurs early during task handling.
  • Memory promotion on feature completion: Apply v2’s feature_complete behavior and the resulting memory_promote suggestions so feature learnings persist.

Quick Start

Ask an AI assistant to review your maestroCLI v2 migration changes by having it identify any remaining v1 “context” imports, invalid task states, and missing v2 patterns in the files you touched.

Frequently Asked Questions about maestro-v2-migration

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

FAQPage Schema
How do I migrate maestroCLI context imports to the v2 memory architecture?▼

To migrate maestroCLI context imports to v2 memory, you must rename ContextPort to MemoryPort, FsContextAdapter to FsMemoryAdapter, and contextAdapter to memoryAdapter, aligning filesystem path expectations with the new memory terminology.

What are the valid task lifecycle states in maestroCLI v2?▼

The valid task lifecycle states in maestroCLI v2 are open, claimed, done, and blocked. You must update task state handling to enforce only these four transitions and correct any invalid legacy state values.

How does the v2 pre-agent hook handle task specs and tool detection?▼

The v2 pre-agent hook injects task specs and performs tool detection early during task handling, operating alongside the default plain-file task backend (fs) while maintaining alignment with the TaskPort interface.

What is memory promotion behavior when a feature completes in maestroCLI v2?▼

Memory promotion in maestroCLI v2 triggers via the feature_complete behavior, generating memory_promote suggestions so that feature learnings persist and are correctly stored using the updated memory adapter.

Do I need to update the execution layer when moving to maestroCLI v2?▼

Yes, moving to maestroCLI v2 requires adapting to the removal of the v1 execution layer, selecting the default plain-file task backend (fs), and ensuring your code remains aligned with the TaskPort interface.

Related Skills

Explore More Software Engineering Skills→
rezicsrezics
6

better-result-migrate-v2

Migrate better-result TaggedError usage from v1 classes to v2 factories.

Official
Advanced
jayantakjayantak
3

session

Track tasks, projects, and sessions in an Obsidian vault.

Community
Advanced
wrsmith108wrsmith108
5

Hooks Automation

Automate Claude Code hooks with MCP integration for multi-agent workflows.

Community
Intermediate
w5851w5851
2

vscode-symbol-tools

Locate code symbol usages via language server and apply semantic renames.

Community
Intermediate