12 Solution Evaluation And Transition

Solution Evaluation And Transition Skill

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.
• 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

Workflow

1. Inspect the required inputs and log the exact sources, versions, and unresolved assumptions.
2. Apply this skill's existing domain workflow and decision rules to produce Solution evaluation and transition plan.
3. Stop when a required source, accountable decision owner, or deterministic test oracle is absent.
4. Recover by preserving valid work, marking the blocked scope, and returning the narrowest qualified artefact plus the next evidence needed.

Outputs

Evidence Produced

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

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.

References

• Skill authoring and release standard

Overview

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

Quick Reference

Core Instructions

Step 1: Assess Transition Scope

Document who must change, including:

• end users
• approvers or supervisors
• support teams
• operations teams
• downstream systems or partners

Step 2: Define Readiness Evidence

Collect evidence required for transition:

• requirement and test coverage
• unresolved defect or risk summary
• training or enablement readiness
• support and operations readiness
• rollback and cutover preparedness

Step 3: Plan Organizational Transition

Specify:

• training activities
• communications
• cutover sequence
• support model during hypercare
• ownership after handoff

Step 4: Frame the Go/No-Go Decision

State:

• go criteria
• no-go triggers
• conditional-go criteria
• approvers
• evidence package required

Step 5: Define Solution Evaluation Measures

Define post-launch evaluation measures:

• adoption
• task completion
• error or defect rate
• operational burden
• user satisfaction
• business outcome measures tied to project goals

Step 6: Write Output

Write projects/<ProjectName>/<phase>/<document>/solution_evaluation_transition_plan.md with transition actions, readiness gaps, decision criteria, and evaluation metrics.

Common Pitfalls

• Launching without naming operational owners
• Treating training as optional for behavior-changing systems
• Using vague go/no-go criteria
• Measuring only delivery output instead of actual solution performance

Verification Checklist

• Transition-affected groups are identified.
• Readiness evidence is defined and reviewed.
• Go/no-go criteria are explicit and measurable.
• Adoption, support, and hypercare plans are documented.
• Post-implementation evaluation metrics are tied to goals.

For Java/JVM platform or framework transitions, apply the Java enterprise requirements overlay to define compatibility stages, reconciliation, rollout stops, recovery and retirement evidence.