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.