promote-plan

Name: promote-plan
Availability: InStock
Author: jmagar

Move plan files between proposed/, active/, and completed/ with git mv.

Updated Aug 27, 2026

Search Tags:#documentation #cross-references #git-mv #plan-management #execution-plans #drift-detector

Ready to run

npx skills add https://github.com/jmagar/rust-bin --skill promote-plan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: promote-plan
Source: https://github.com/jmagar/rust-bin/tree/main/.claude/skills/promote-plan
Command: npx skills add https://github.com/jmagar/rust-bin --skill promote-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures execution plans reflect real work by moving plan files between proposed/, active/, and completed/ and by updating cross-references and Status lines.

Core Features & Use Cases

Move plan files between stages (proposed/ → active/ → completed/) with git mv to preserve history.
Update the plan metadata (Status lines) and fix cross-references across docs.
Abandon or revert plans safely when work is halted or superseded.

Quick Start

Use the promote-plan skill to advance a plan from proposed/ to active/ or to completed/ after verification.

Frequently Asked Questions about promote-plan

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

FAQPage Schema

How do I move execution plans between proposed, active, and completed directories?▼

Move execution plans between proposed, active, and completed directories using git mv to preserve file history. This aligns the plan location with its real-world state while updating cross-references across documentation.

What is plan drift and when should I update plan metadata?▼

Plan drift occurs when a plan's real-world state diverges from its directory state. You should update plan metadata and Status lines whenever work starts, progresses, completes, or when drift-detector flags trigger.

Can I abandon or revert an active execution plan safely?▼

Yes, you can abandon or revert active execution plans safely when work is halted or superseded. The process moves plan files and updates cross-references to maintain overall documentation consistency.

Does promoting a plan with git mv preserve cross-references in documentation?▼

Yes, promoting a plan with git mv preserves file history and fixes cross-references across docs. It ensures a Status line is present and updated so that documentation accurately reflects reality.

What's the best way to fix execution plan drift detected in a git repository?▼

The best way to fix execution plan drift is to move plan files to the correct stage directory using git mv and update their Status lines. This resolves location mismatches flagged by drift-detector triggers.