flow-revise

Update project specifications and plans with revision logging and Beads synchronization.

15|4|Updated Jan 20, 2026
One-click install
npx skills add https://github.com/cofin/flow --skill flow-revise
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flow-revise
Source: https://github.com/cofin/flow/tree/main/templates/codex/skills/flow-revise
Command: npx skills add https://github.com/cofin/flow --skill flow-revise

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the common challenge of adapting project specifications and plans when the implementation process uncovers unforeseen issues or requires adjustments.

Core Features & Use Cases

  • Dynamic Spec/Plan Updates: Allows for modifications to spec.md and learnings.md based on real-world implementation feedback.
  • Revision Logging: Maintains a detailed history of all changes made to specs and plans, including the reasons and types of revisions.
  • Beads Integration: Seamlessly updates the Beads memory store with new tasks or revised notes, ensuring persistent state management.
  • Use Case: During development, a programmer discovers that a planned feature is technically infeasible within the given constraints. They use flow-revise to update the spec.md to reflect the new constraints and log the reason for the change.

Quick Start

Use the flow-revise skill to update the spec for flow_id 123, specifying that the revision is for the plan and the reason is a change in user requirements.

Frequently Asked Questions about flow-revise

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

FAQPage Schema
How do I update project specifications when implementation reveals issues?

Updating project specifications when implementation reveals issues involves modifying spec.md and learnings.md based on real-world feedback. flow-revise manages revisions for specific flow IDs, logs reasons, and synchronizes changes with the Beads memory store.

What is the best way to log reasons for revising a development plan?

Logging reasons for revising a development plan requires maintaining a detailed history of all changes made to specifications. flow-revise records the specific reasons and types of revisions directly within the project documentation.

Can I synchronize updated documentation with the Beads memory store?

Yes, you can synchronize updated documentation with the Beads memory store. flow-revise seamlessly updates the memory store with new tasks or revised notes, ensuring persistent state management across the development workflow.

When do I need to revise a spec during the development workflow?

You need to revise a spec during the development workflow when a planned feature becomes technically infeasible within given constraints. flow-revise updates the spec.md to reflect new constraints and logs the specific reason for the change.

Does flow-revise support dynamic task creation within Beads?

Yes, flow-revise supports dynamic task creation and updates within Beads. It allows developers to specify a revision for a specific flow ID, such as updating a plan due to a change in user requirements, and synchronizes the new tasks automatically.