Skill

plan-manager

Creates, tracks, and coordinates execution of plans as local JSON files via npx rosettify CLI subcommands. For orchestrators and subagents in plan-driven workflows.

Node

Bash

cli-tools

automation

npx claudepluginhub griddynamics/rosetta --plugin core

Configuration

Model: sonnet

Tool Access

This skill is limited to using the following tools:

Bash(npx:*)

Preview

<plan-manager>

Supporting Assets

assets/pm-schema.md

SKILL.md

Similar Skills

orchestrate

Executes multi-phase implementation plans by dispatching task implementers and reviewers, tracking progress per task in plan.json. Use for independent tasks in sessions.

5 files

claude-caliper-workflow

execute-plan

Executes finalized plans by loading task files, building dependency graphs, parallelizing topological task execution via subagents for complex work or inline for simple actions.

amplify

run-plan

Executes written implementation plans: loads and critically reviews them, runs tasks in dependency order with parallel dispatch, separate worker-validator subagents, and verifies completion.

engineering-discipline

Stats

Parent Repo Stars15

Parent Repo Forks6

Last CommitApr 6, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Senior execution planner and tracker for plan-driven workflows.

<when_to_use_skill>

Primary plan manager for orchestrators and subagents. Creates, tracks, and executes plans as local JSON files.

</when_to_use_skill>

<core_concepts>

Rosetta prep steps completed
Plan file lives in FEATURE PLAN folder: <feature_plan_folder_full_path>/plan.json
CLI: npx rosettify plan <subcommand> <plan_file> [args...]
Always use full absolute paths for the plan file
Seven subcommands: help, create, next, update_status, show_status, query, upsert
Resume behavior: next returns four groups: (1) in_progress steps (resume=true), (2) open eligible steps, (3) blocked steps (previously_blocked=true), (4) failed steps (previously_failed=true)
Phases are sequential: steps from a later phase do not appear until all steps in earlier phases are complete
Status propagation: bottom-up only (steps -> phases -> plan); plan root status is always derived, never set directly
Phase status updates are rejected (phase_status_is_derived); entire_plan target is rejected for update_status (invalid_target)
upsert silently ignores status fields in patch -- only update_status modifies status
ACQUIRE plan-manager/assets/pm-schema.md FROM KB for data structure reference

</core_concepts>

Orchestrator flow:

Create plan: npx rosettify plan create <plan_file> '<json>' -- see pm-schema.md for JSON structure
Upsert phases and steps: npx rosettify plan upsert <plan_file> entire_plan [kind] '<json>'
Delegate steps to subagents -- pass plan file path and step IDs
Loop: call next until plan_status: complete and count: 0

Subagent flow:

Get next steps: npx rosettify plan next <plan_file> [limit]
Check resume flag -- if true, continue interrupted work; if false, start fresh
Execute step
Update: npx rosettify plan update_status <plan_file> <step-id> complete
Repeat from step 1

<validation_checklist>

npx rosettify plan help exits without error and returns structured help JSON
show_status output: plan root status is derived (never manually set)
next output: in_progress steps appear before open steps; blocked and failed steps are included with flags
show_status phase status matches aggregate of its steps after update_status

</validation_checklist>

Not checking resume flag on next results -- causes duplicate work on resumed sessions
Forgetting update_status after step completion -- plan remains stale
Plan root status cannot be set directly -- it is always derived from phases
Attempting to set phase status directly -- rejected as phase_status_is_derived

Asset: ACQUIRE plan-manager/assets/pm-schema.md FROM KB -- plan JSON structure
Flow: USE FLOW adhoc-flow