plan-dev-modify

Modify planning documents to update TASK-N, resolve markers, and sync statuses with issues.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/oogDZ/2 --skill plan-dev-modify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-dev-modify
Source: https://github.com/oogDZ/2/tree/main/.claude/skills/plan-dev-modify
Command: npx skills add https://github.com/oogDZ/2 --skill plan-dev-modify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Modify planning documents to keep development plans aligned and synchronized.

Core Features & Use Cases

  • Update existing plan-dev documents: refresh TASK-N, resolve markers, and translate statuses.
  • Ensure synchronization with issue tracker to reflect conflicts and progress.
  • Audit trail and SSOT alignment for specs and development workflows.

Quick Start

Run the plan-dev-modify command with the path to the plan document to update TASK-N, statuses, and sync with issues.

Frequently Asked Questions about plan-dev-modify

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

FAQPage Schema
How do I update task status transitions in development plan documents?

You can update task status transitions in development plan documents by running the modify command with the file path. It translates DRAFT to WAITING, applies RUNNING edits, and refreshes TASK-N entries to keep plans synchronized.

How do I resolve CONFLICT markers by syncing plan documents with issue tracking?

To resolve CONFLICT markers, the workflow syncs plan documents with the issue tracker across specs. This handles conflict resolution and reflects current progress, ensuring development plans remain aligned with tracked issues.

What is the best way to maintain an audit trail for spec and development workflow modifications?

The best way to maintain an audit trail for spec modifications is using a structured plan management workflow. It enforces SSOT alignment and applies safe, auditable edits to development plans and issue tracking synchronization.

Can I apply structured plan management to update existing plan-dev documents without breaking traceability?

Yes, you can update existing plan-dev documents without breaking traceability. The process resolves markers, refreshes TASK-N identifiers, and applies status changes while enforcing SSOT alignment across the development workflow.

Do I need a specific issue tracker to synchronize plan development statuses?

You need an issue tracker integrated into your workflow to synchronize plan development statuses and handle CONFLICTs. The modification process syncs plan documents with issues across specs to maintain accurate traceability.

Why does plan development modification fail to apply RUNNING edits to DRAFT statuses?

Plan development modification applies specific status transitions like translating DRAFT to WAITING before applying RUNNING edits. Attempting to apply RUNNING edits directly to a DRAFT status bypasses the required workflow transition sequence.