update

Apply inline annotations to update plan.md and implementation phase files.

Updated Nov 15, 2025
One-click install
npx skills add https://github.com/cloudvoyant/claudevoyant --skill update-cloudvoyant
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update
Source: https://github.com/cloudvoyant/claudevoyant/tree/main/plugins/spec/skills/update
Command: npx skills add https://github.com/cloudvoyant/claudevoyant --skill update-cloudvoyant

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of applying specific instructions and changes directly within plan files, streamlining iterative development and task management.

Core Features & Use Cases

  • Inline Annotation Processing: Understands and applies > and >> annotations for tasks like marking items complete, removing tasks, or rewriting content.
  • Automated Plan Updates: Modifies plan files based on direct instructions, reducing manual editing.
  • Use Case: After a discussion, you add notes like > rewrite this phase for OAuth or 1. [ ] Task name >> mark done directly into your plan.md. Running this Skill applies these changes automatically.

Quick Start

Use the update skill to apply annotations to the 'project-alpha' plan.

Frequently Asked Questions about update

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

FAQPage Schema
How do I apply inline annotations to update markdown plan files?

To apply inline annotations to update markdown plan files, use this Skill to process `>` and `>>` syntax within your `plan.md` and phase files, automatically modifying task status and structure based on your direct notes.

What is the best way to automate task status updates in a development plan?

Automating task status updates in a development plan is best achieved by adding `>> mark done` annotations directly to your tasks and running this Skill to apply the changes automatically across the scoped directory.

How does inline annotation processing work for iterative plan refinement?

Inline annotation processing for iterative plan refinement works by scanning `.spec/plans/` for `>` and `>>` markers to execute instructions like rewriting content or removing tasks without manual file editing.

Can I use inline annotations to rewrite specific phases in my plan files?

Yes, you can use inline annotations to rewrite specific phases in your plan files by adding notes like `> rewrite this phase` directly into `implementation/phase-N.md` files and running the update Skill to apply the changes.

Does this automated task management approach require a specific directory structure?

Yes, this automated task management approach requires a specific directory structure, scoping exclusively to `.spec/plans/{plan-name}/` to locate and modify your `plan.md` and `implementation/phase-N.md` files.