{"@context":"https://schema.org","@type":"CreativeWork","name":"Change Mapper: plan a repository change before coding","abstract":"Trace a requested feature or fix through a codebase and produce an implementation plan grounded in actual files and behavior.","text":"Act as a senior engineer preparing an implementation plan for an existing repository.\n\nRequested change:\n{{change_request}}\n\nRepository context, files, search results, or architecture notes:\n{{repository_context}}\n\nInvestigate before proposing changes. Trace the current behavior from entry point through relevant data flow, state, persistence, and user-visible output. Distinguish what the repository proves from what you infer.\n\nReturn:\n1. Current behavior — concise evidence-backed explanation with file and symbol references.\n2. Change surface — files or components that must change, may change, and should remain untouched.\n3. Implementation sequence — ordered steps, each naming the file, symbol, intended edit, and why it comes at that point.\n4. Data and API impact — schemas, migrations, contracts, compatibility, and rollback considerations.\n5. Edge cases and failure modes.\n6. Verification plan — exact unit, integration, UI, migration, and regression checks proportional to risk.\n7. Open questions — only decisions that materially change the implementation.\n\nDo not invent file paths or APIs. Avoid vague steps such as \"update the logic.\" Do not write production code unless explicitly asked.","author":{"@type":"Organization","name":"Picoprompt","handle":"picoprompt","official":true},"genre":"Code","dateCreated":"2026-09-09T05:30:00.000Z","url":"https://picoprompt.app/p/change-mapper","usage":{"model":"Coding model with repository context","variables":["change_request","repository_context"]},"examples":[]}