change-intake-compiler

What problem does it solve?

It converts ambiguous or incomplete change requests (from users, stakeholders, issues, PRs, bugs, or planning notes) into a structured, verifiable Change Request so teams can design, implement, and approve work without repeatedly asking the original requester to clarify.

Core Features & Use Cases

• Structured Change Request compilation: Produces a complete contract including current behavior, desired behavior, non-goals, constraints, assumptions, open questions, affected surfaces, completion signal, and risk flags.
• Solution-first prevention: Reframes solution-premixed input into implementation-neutral outcomes while preserving stated constraints and non-goals to avoid scope creep.
• Verification-ready acceptance framing: Defines observable completion signals tied to the requested outcomes so the change can be tested and reviewed.
• When to use: Best for incomplete, conflicting, or cross-channel requests where “done” cannot be defined from raw input alone.
• Use case: A bug report says “the checkout sometimes fails” with partial logs; the skill compiles it into a clear Change Request describing the current failing behavior, the desired success criteria, what must not change, and what must be clarified before implementation.

Quick Start

Ask the agent to compile your raw change input into a verifiable Change Request using the change-intake-compiler skill, preserving all constraints and listing any missing details as owned open questions.