plan-manager

<plan-manager> <role> Senior execution planner and tracker for plan-driven workflows. </role> <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> - All Rosetta prep steps MUST be FULLY completed, load-context skill loaded and fully executed - Plan file lives in FEATURE PLAN folder: `<feature_plan_folder_full_path>/plan.json` - CLI: `npx rosettify@latest plan <subcommand> <plan_file> [args...]` - Always use full absolute paths for the plan file - Six subcommands for `plan` command: `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> <process> **Orchestrator flow:** 1. Create plan: `npx rosettify@latest ...