reversa-add

Registers and implements small amendments to the active forward-cycle feature specification.

1.5k|405|Updated Apr 26, 2026
One-click install
npx skills add https://github.com/sandeco/reversa --skill reversa-add
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reversa-add
Source: https://github.com/sandeco/reversa/tree/main/agents/reversa-add
Command: npx skills add https://github.com/sandeco/reversa --skill reversa-add

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After a feature is delivered, small adjustments (text changes, spacing, loading indicators) often get applied directly in chat, leaving the specification behind the code. This Skill closes that gap by recording each amendment in the feature's requirements.md and implementing it in the same step, keeping spec and code synchronized without running the full forward pipeline.

Core Features & Use Cases

  • Spec-first amendments: Assigns sequential IDs (E001, E002...) and appends each amendment to the requirements.md Emendas section before touching any code.
  • Scope guardrails: Refuses requests that require new dependencies, schema changes, new public surfaces, or auth/payment changes, redirecting them to the full requirements cycle.
  • Traceable closure: Appends completed actions to actions.md, updates the legacy-impact.md affected-files table, and logs each amendment to progress.jsonl.
  • Use Case: After a feature ships, a user asks to enlarge a title and add a loading spinner. The Skill registers both as E001 and E002 in the spec, implements them, and closes the actions in one pass.

Quick Start

Ask the agent to apply a small adjustment to the currently active feature, for example: add a loading indicator to the component the active feature delivered.

Frequently Asked Questions about reversa-add

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

FAQPage Schema
How do I make small changes to a delivered feature without rerunning the full pipeline?

Invoke the amendment flow on the active feature: it records the change in requirements.md under an Emendas section with a sequential ID, implements only that change, then closes the action in actions.md and logs it to progress.jsonl.

What kinds of changes qualify as amendments versus new features?

Amendments are small adjustments to files the active feature delivered, like text, styling, or loading states. Anything needing new dependencies, schema changes, new endpoints, or auth and payment modifications is rejected and routed to the full requirements cycle.

Can I run an amendment before the feature coding phase finishes?

No. The Skill aborts if there is no active feature or if legacy-impact.md is missing, meaning the coding phase has not completed. You must finish the coding step first so there is a delivery to amend.

Why does the amendment get recorded in the spec before the code changes?

Recording first prevents a window where code is ahead of the specification, which is the exact drift problem this workflow solves. If implementation later reveals the change is too large, the amendment is marked interrupted in the spec.

Which AI coding agents support this amendment workflow?

It is compatible with Claude Code, Codex, Cursor, Gemini CLI, and other agents supporting the Agent Skills format, as declared in the Skill's compatibility metadata.