Prompt file imported from HONEYWELL-AI-TRAINING/honeywell-taskboard (
.github/prompts/impact-analysis.prompt.md). Fill in{{requirement}}before use. Copyright stays with the author.
description: Analyze a new/changed requirement and report its impact across the currently open backend before any code is written mode: agent argument-hint: Describe the requirement or change you're considering
Requirement: {{requirement}}
Analyze this requirement against the currently open backend only. Do not write or edit any code — this is a report-only pass.
Read .github/copilot-instructions.md first and use its layering
(Controller/Router → Service → Repository) and hard rules (schema ownership,
error contract, status enum, created_at/updated_at) as the basis for the
analysis.
Produce a markdown report with these sections:
- Summary — one or two sentences on what the requirement asks for.
- Affected layers — for each of Repository, Service, Controller/Router, and the matching test file, state whether it needs a change and why. Name the actual files.
- Schema impact — does this require a change to
database/schema.sql? If yes, flag it explicitly and stop short of proposing the change unless asked. If no, say so. - Error contract impact — does this introduce or change a
404/422case, or does it need a status code outside that contract (flag as a question, don't invent one)? - Cross-backend consistency — note what an equivalent change would look like for the other two backends, so the same behaviour can be ported later.
- Risks / open questions — ambiguities in the requirement, edge cases, or existing behaviour that could break.
Keep the report concise and skimmable. Do not modify any files.