SA

    Spec Amend

    1

    Surgically update specs, design, tasks, and test files to maintain a living, auditable contract when requirements change.

    $9

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more
    SA

    Spec Amend

    Example session with this skill installed

    Amend the export-users specs: include display_name in the CSV too.

    • Read your context and instructions
    • Compiled the spec amend

    I read spec.md, design.md, tasks.md and testing.md, then made the smallest edits that reflect the new requirement. No source code was touched. The change is recorded in the amend log.

    What changed

    FileChange
    spec.mdRequirement 1 now lists display_name; one scenario updated
    design.mddisplayName added to the UserExportRow contract
    tasks.mdNew task T6 added; done tasks stay ticked
    testing.mdTC1 expected header updated

    Diffs

    -1. The system SHALL export id, email and created_at for every active user.
    +1. The system SHALL export id, email, display_name and created_at for every active user.
    
     interface UserExportRow {
       id: string;
       email: string;
    +  displayName: string;
       createdAt: string;
     }
    
     - [x] T3. add serializer for UserExportRow
    +- [ ] T6. add displayName column to the serializer and the user query
    

    T3 stays ticked because the code exists. T6 tells the implementer what to adjust.

    Amend log (end of spec.md)

    
    ## Amend log
    - 2026-01-15 - Include display_name too - files: spec.md, design.md, tasks.md, testing.md
    

    Next steps

    1. Review the four small diffs.
    2. Run the implementation step so T6 is built against the updated contract.

    PASS

    Amend log (end of spec.md

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Specs often rot the moment a requirement changes, leading to a permanent drift between documentation and code. This skill enforces a "specs-first" change management workflow, ensuring that every shift in project scope is surgically recorded across your entire documentation suite before a single line of code is touched.

    What it does

    • Surgical editing updates only the specific requirements, technical decisions, or tasks affected by new feedback.
    • Audit logging appends verbatim user feedback and timestamps to a persistent amend log in the spec file.
    • Task invalidation manages task lists by marking obsolete items and adding new ones without erasing history.
    • Coherence checking verifies that changes are reflected consistently across spec, design, tasks, and testing files.
    • Scope guarding detects when a change is too large for an amendment and triggers a full proposal restart.

    How it works

    1. Analyze input against existing spec.md, design.md, tasks.md, and testing.md files.
    2. Identify gaps in logic or ambiguity in the feedback, stopping for clarification if needed.
    3. Execute edits using non-destructive operations to maintain a clear audit trail of what changed and why.
    4. Log the event with an ISO date and the exact feedback text.
    5. Issue a verdict of PASS or GAP based on the internal coherence of the updated files.

    Frameworks & tools

    This tool is language-agnostic and works with any codebase using Markdown-based documentation (spec.md, design.md, tasks.md, testing.md).

    Why this beats prompting it yourself

    Generic prompts often cause LLMs to rewrite entire files, losing context and history. This skill enforces strict surgical edit rules and prevents the "unticking" of completed tasks, maintaining an honest project history that generic instructions usually ignore.

    Use cases

    • Update a feature requirement after a stakeholder changes their mind mid-sprint.
    • Adjust technical design decisions without losing the original context of the architecture.
    • Re-align testing suites and task lists when a specific edge case is redefined.
    • Maintain a regulatory or project-governance audit trail of why requirements changed.

    Known limitations

    Does not edit source code. Requires existing Markdown documentation files to function. Restricted to surgical edits rather than full-scale project pivots.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse All Claude Skills.

    Does not edit source code. Requires existing Markdown documentation. Explicitly stops if feedback is ambiguous or requires a total project restart.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 19 days ago

    Permissions

    Read Files
    Write Files
    Listed19 days ago

    What's inside

    Frequently Asked Questions

    This skill acts as a documentation surgeon; instead of rewriting files from scratch, it identifies and updates only the specific sections of your spec, design, and task files affected by a change, preserving all surrounding context and history.

    It is designed for any agentic workflow or IDE extension (like Cursor, Windsurf, or GitHub Copilot) that can read and write Markdown files within a workspace.

    The skill requires four core Markdown files in your project: spec.md, design.md, tasks.md, and testing.md. Once these files exist, the skill can immediately begin managing amendments and audit logs.

    No, this skill intentionally focuses on the 'specs-first' layer; it ensures your documentation and logic are sound before you or your agent begin the coding phase to prevent expensive implementation errors.

    When a change is too massive for a surgical amendment, the skill issues a 'Scope Guard' alert, signaling that the change requires a new full proposal rather than a simple edit to maintain project integrity.

    Every purchase includes the core skill logic, a set of templates for the required Markdown files, and a guide on integrating the 'specs-first' workflow into your existing development routine.