revise

Revise project plans and specifications based on critique findings.

13|1|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/davidabeyer/formaltask --skill revise
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: revise
Source: https://github.com/davidabeyer/formaltask/tree/main/skills/revise
Command: npx skills add https://github.com/davidabeyer/formaltask --skill revise

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of addressing feedback and making corrections to existing project plans and specifications, ensuring that all identified issues are thoroughly resolved.

Core Features & Use Cases

  • Unified Revision: Handles revisions for both project plans and detailed specifications.
  • Automated Verification: Verifies fixes against the codebase before and after application.
  • Use Case: After a code review flags several issues in your project's plan and specs, use this Skill to automatically apply the necessary fixes, verify their correctness, and commit the changes.

Quick Start

Use the revise skill to fix the plan and specs for the project named 'formaltask'.

Frequently Asked Questions about revise

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

FAQPage Schema
How do I fix project plans and specs after a code review?

To fix project plans and specs after a code review, you revise the documents based on critique findings. This ensures all identified blockers are addressed and tracks the updated code and documentation through a git commit.

What is the best way to apply critique findings to project specifications?

The best way to apply critique findings to specifications is through an iterative revision workflow. This approach verifies the corrections against the codebase before and after application, ensuring all flagged issues are thoroughly resolved.

Does revising project plans require validating changes against the codebase?

Yes, revising project plans requires validation against the codebase. The process verifies fixes before and after application to ensure correctness, and uses a git commit to track the resolved blockers and updated documentation.

Can I use a unified workflow to update both project plans and detailed specifications?

Yes, you can use a unified revision workflow to update both project plans and detailed specifications. This handles corrections for both document types, automatically verifying the fixes against the codebase and committing the changes.

What are the limitations of automated plan and spec revision?

A limitation of automated plan and spec revision is its dependency on existing critique findings to function. It requires a validation step against the codebase and a git commit to properly track the applied corrections.