force-solution

Solution — From Requirements and Evaluation to Solution Document

Turn approved requirements and evaluation documents into a concrete solution document.

HARD GATE: Do NOT write implementation code. Your only output is a solution document.

Announce at start: "I'm using the force-solution skill to create a solution document from requirements and evaluation."

Save documents to: docs/solution/YYYY-MM-DD-<feature-name>-solution-vN.md

---

Phase 1: Read Inputs

1. Check docs/requirements/ for the latest relevant requirements document.
2. Check docs/evaluation/ for the latest relevant evaluation document.
3. Surface the selected document paths to the user before proceeding.
4. If no requirements document exists, ask the user to create or provide one first.
5. If no evaluation document exists, ask the user to create or provide one first. Do not invent evaluation criteria inside this skill.

Read the chosen documents thoroughly. Extract the problem statement, boundaries, criteria, constraints, and unresolved gaps.

---

Phase 2: Map Solution to Judgment

For each must-pass criterion in the evaluation document, explicitly identify how the solution will satisfy it.

Also identify:

• should-pass items covered by the solution
• should-pass or nice-to-have items intentionally deferred
• constraints that shape the design

If any must-pass item is not addressed, the solution is incomplete and must be revised before delivery.

---

Phase 3: Write Solution Document

Save to docs/solution/YYYY-MM-DD-<feature-name>-solution-vN.md with this structure:

# [Feature Name] Solution

## Inputs
- Requirements: `docs/requirements/<filename>.md`
- Evaluation: `docs/evaluation/<filename>.md`

## Goal
What this solution is trying to achieve.

## Approach
High-level design and why it fits the current constraints.

## Mapping to Evaluation
### Must-pass
| Criterion | Solution response |
|---|---|
| [criterion] | [how it is addressed] |

### Deferred items
| Criterion | Reason for deferral |
|---|---|
| [criterion] | [why] |

## Risks and Gaps
What remains uncertain.

## Implementation Notes
The concrete work an implementer should be aware of, without writing implementation code.

---

Rules

• Create a new versioned file instead of overwriting an older one.
• Address every must-pass item explicitly.
• Call out uncovered should-pass and nice-to-have items rather than silently dropping them.
• Do not generate implementation code.

---

Delivery

After saving the document:

"Solution document complete and saved to docs/solution/<filename>.md. It maps the current approach back to the selected requirements and evaluation inputs."