revision

Revises existing plans using PLAN REVISION tags while preventing scope drift into new tasks.

Updated Sep 2, 2026
One-click install
npx skills add https://github.com/Dazlarus/karl-code --skill revision-dazlarus
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: revision
Source: https://github.com/Dazlarus/karl-code/tree/main/.agents/skills/revision
Command: npx skills add https://github.com/Dazlarus/karl-code --skill revision-dazlarus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When users ask to modify an existing plan, AI assistants often drift into creating entirely new plans, adding unrelated features, or jumping into implementation. This Skill enforces disciplined plan revision behavior so changes stay focused on the original plan. ## Core Features & Use Cases - Revision Tag Enforcement: Ensures all plan modifications use <PLAN REVISION> tags instead of <PLAN> tags, keeping revision output distinct from new plans. - Drift Prevention: Blocks new-task drift, context loss, and implementation drift by constraining revisions to the existing plan's scope and approach. - Structured Change Tracking: Requires a clear statement of what changed, updated file lists, and updated change lists referencing the previous plan. - Use Case: A user says "Revise the plan to add caching and remove Redis." The Skill produces a focused <PLAN REVISION> block listing only those changes, without inventing new features or starting implementation. ## Quick Start Ask the assistant to revise the current plan, for example: "Revise the plan to use PostgreSQL instead of MongoDB."

Frequently Asked Questions about revision

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

FAQPage Schema
How do I revise an existing plan without creating a new one?▼

Ask to revise, update, or modify the plan, and the revision skill responds with a PLAN REVISION block stating what changed, updated files, and updated changes. It references the existing plan rather than starting from scratch.

What is the difference between a plan revision and a new plan?▼

A revision modifies an existing plan using PLAN REVISION tags and keeps the original approach unless explicitly changed. A new plan uses PLAN tags and starts fresh with no prior context.

When should the revision skill not be used?▼

Do not use it for creating new plans from scratch, explaining an existing plan, or unrelated tasks like fixing bugs or implementing features. Those cases use the planning skill or direct execution instead.

How does the revision skill prevent scope drift?▼

It restricts output to the existing plan's scope, forbids adding unrelated features, blocks implementation activity, and requires a checklist confirming the revision stays focused before emitting output.

Can I ask for multiple revisions to the same plan?▼

Yes. Each revision references the most recent plan version, and cumulative changes can be tracked across revisions. You can also request returning to an earlier version if plan history is available.