Use when planning adoption, readiness, go/no-go evidence, transition, and post-implementation outcome evaluation; use go-live-readiness for the release-day operational gate.
Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.
Quelldateien prüfen
Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.
Use when planning adoption, readiness, go/no-go evidence, transition, and post-implementation outcome evaluation; use go-live-readiness for the release-day operational gate.
planning adoption, readiness, go/no-go evidence, transition, and post-implementation outcome evaluation; use go-live-readiness for the release-day operational gate.
Use this procedure when the required source artefacts are available and Solution evaluation and transition plan is the next lifecycle deliverable.
Do Not Use When
Use go-live-readiness when that neighbouring route owns the decision or deliverable.
Do not invent missing project evidence, standards clauses, thresholds, or stakeholder decisions.
Required Inputs
Artefact
Source or provider
Required?
Behaviour when missing
Approved requirements, delivered solution evidence, stakeholder impacts, and success measures
Project sponsor, operations, users, and delivery records
Yes
Stop the affected step, name the missing source, and return only a qualified gap record.
Workflow
Inspect the required inputs and log the exact sources, versions, and unresolved assumptions.
Apply this skill's existing domain workflow and decision rules to produce Solution evaluation and transition plan.
Stop when a required source, accountable decision owner, or deterministic test oracle is absent.
Recover by preserving valid work, marking the blocked scope, and returning the narrowest qualified artefact plus the next evidence needed.
Outputs
Artefact
Consumer
Acceptance condition
Solution evaluation and transition plan
Sponsor, adoption leads, operations, and benefits owner
Required sections are populated, source links resolve, and every material requirement or decision has an observable review or test oracle.
Evidence Produced
Evidence
Reviewer
Acceptance condition
Source, decision, trace, and validation record for Solution evaluation and transition plan
Requirements quality reviewer
Inputs used, decisions made, checks run, failures, and unassessed items are explicit.
Capability and permission boundaries
Read and search are required. This procedure is read-only by default. Editing the reviewed artefact, publishing, production mutation, destructive action, spending, or certification requires explicit authority.
Degraded mode
Fallback: if a required file, reviewer, standard source, network check, renderer, or execution capability is unavailable, return the narrowest useful qualified result and mark the affected check not assessed; never convert an unassessed check into a pass.
Decision Rules
Choice or condition
Action
Failure or risk avoided
A transition dependency has no owner or observable readiness evidence
Block the affected transition milestone and assign evidence ownership.
Go-live without operational or organisational readiness.
Required inputs and test oracles are complete
Continue through the existing workflow and record evidence.
A deliverable whose acceptance cannot be reproduced.
A mandatory source or owner is missing
Stop the affected branch and issue a qualified gap record.
Fabricated context or unauthorised decisions.
Quality Standards
Preserve stable identifiers and bidirectional traceability from project evidence to Solution evaluation and transition plan and its acceptance checks.
Apply ISO/IEEE measures only with a named metric, method, threshold, evidence source, and responsible reviewer; run the anti-slop gate before release.
Anti-Patterns
Producing Solution evaluation and transition plan from assumed context. Fix: cite the project source or mark the scope blocked.
Accepting a material requirement without a deterministic oracle. Fix: add a measurable result, boundary, and verification method.
Crossing into go-live-readiness without routing the decision. Fix: hand off the named input and preserve trace links.
Treating an unavailable check as passed. Fix: mark it not assessed and state the release consequence.
Claiming standards, statutory, or stakeholder approval without evidence. Fix: cite the source and reviewer or qualify the claim.
This skill closes the gap between completed requirements or delivery artifacts and real organizational adoption. It plans transition activities, readiness evidence, go/no-go framing, post-implementation evaluation, and success measurement so the engine supports actual solution rollout, not only analysis and design.
When to Use
When requirements, design, testing, or deployment artifacts are mature enough for rollout planning
Before a pilot, cutover, or formal go/no-go decision
When the project changes user behavior, operating procedures, or support responsibilities
After early release to define solution performance evaluation criteria
