---
name: scorpio-solution
description: Translate an approved objective package into SOLUTION-BRIEF.md and canonical TASK-PLAN-HANDOFF.json without reopening package choice.
---

# Solution Definition

A bounded bridge skill for the seventh stage of `scorpio objective`. It converts one approved solution package into implementation-facing planning artifacts and preserves the rule that `scorpio-task-plan` remains the exclusive writer of `{docs.tasks}/**`.

## Purpose

This skill exists to bridge strategy into implementation planning.

It must:

1. consume the approved package and recommendation context
2. translate strategy into product-definition terms
3. write `SOLUTION-BRIEF.md`
4. write a canonical `TASK-PLAN-HANDOFF.json`
5. avoid reopening package selection or generating tasks directly

## Inputs

Read:

1. `{docs.planning}/OBJECTIVE-PARAMETERS.json`
2. `{docs.planning}/SOLUTION-PACKAGES.json`
3. `{docs.planning}/RECOMMENDED-SOLUTION.md`
4. any critique findings that materially constrain implementation

Use the approved package recorded by the runtime or request-scoped objective state. Do not re-run strategic choice.

## Shared Rules

1. Bridge the approved package only.
2. Preserve the approved constraints and tradeoffs.
3. Turn strategy into roles, stories, flows, and decisions.
4. Keep downstream task generation bounded and normalized.
5. Do not reopen package selection.
6. Fail clearly if no approved package is recorded.

## Bridge Contract

The resulting artifacts should:

1. preserve the approved package summary
2. define target roles
3. define prioritized user stories
4. define key flows
5. define product and technical decisions
6. capture constraints and non-goals
7. record instrumentation or validation needs
8. identify bounded implementation slices for task planning

## Required Outputs

Write:

- `{docs.planning}/SOLUTION-BRIEF.md`
- `{docs.planning}/TASK-PLAN-HANDOFF.json`

If the runtime provides a request-scoped objective directory, mirror the artifacts there as well, but keep the root canonical files updated in the same run.

## Canonical Brief Shape

`SOLUTION-BRIEF.md` should include:

1. approved package summary
2. target roles
3. prioritized user stories
4. key flows
5. product decisions
6. technical and business constraints
7. non-goals
8. instrumentation requirements
9. rollout or validation notes

## Canonical Handoff Shape

`TASK-PLAN-HANDOFF.json` must remain valid for `scorpio-task-plan` and should use the normalized contract:

```json
{
  "source_skill": "scorpio-solution",
  "source_artifact": "{docs.planning}/SOLUTION-BRIEF.md",
  "feature_name": "",
  "scope_summary": "",
  "slices": [
    {
      "title": "",
      "type": "Feature | Chore | Test",
      "estimate": "XS | S | M",
      "description": "",
      "files_to_modify": [],
      "acceptance_criteria": [],
      "depends_on": []
    }
  ],
  "constraints": [],
  "test_strategy": {}
}
```

Populate the canonical handoff with bounded slices that preserve the approved package intent. Keep the content normalized so `scorpio-task-plan` can write task files without inference.

## Translation Rules

1. Convert strategy into product definition, not new strategy.
2. Carry trust, compliance, privacy, and validation constraints forward.
3. Keep the handoff bounded enough for task planning.
4. Preserve the approved package identity and rationale.
5. Do not rewrite the business objective.

## Failure Conditions

Fail clearly rather than guessing if:

1. no explicit `approved_package_id` is available from the runtime or request-scoped objective state
2. the approved package is too vague to define roles, stories, or flows
3. critique surfaced a blocking trust, compliance, or reputational issue that remains unresolved
4. the approved package cannot be converted into bounded slices for `scorpio-task-plan`

## What Not To Do

- Do not write `{docs.tasks}/**`.
- Do not edit `SOLUTION-PACKAGES.json`.
- Do not edit `SOLUTION-SCORECARDS.json`.
- Do not edit `RECOMMENDED-SOLUTION.md`.
- Do not reopen package selection.
- Do not generate task files directly.
- Do not bypass `scorpio-task-plan`.

## Handoff

When scorpio-solution is complete, hand `TASK-PLAN-HANDOFF.json` to `scorpio-task-plan`.