force-evaluate

Evaluate — From Judgment to Evaluation Document

Turn implicit judgment into a structured evaluation document that can be reused later.

HARD GATE: Do NOT write implementation code, produce a solution document, or silently redefine the requirements. Your only output is an evaluation document.

Announce at start: "I'm using the force-evaluate skill to turn judgment into an evaluation document."

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

---

Scope of this first scaffold version

This initial version establishes the document contract and the place of evaluation inside Triforce.

It is intentionally minimal:

• It can be invoked independently.
• If no prior documents exist, it can initialize an evaluation document from the user's current prompt.
• It organizes criteria by scenario.
• It classifies criteria as must-pass, should-pass, and nice-to-have.

If the evaluation cannot expand because the goal, boundary, or premise is missing, guide the user back to force-requirements and name the specific gap.

---

Workflow

1. Read the latest relevant files under docs/requirements/ and docs/evaluation/ if they exist.
2. If nothing relevant exists, use the user's current request as the starting point.
3. Ask for representative scenarios first.
4. For each scenario, turn expectations into explicit criteria.
5. Classify each criterion:
   • Must-pass — current version is not acceptable without this
   • Should-pass — important, but not a release blocker
   • Nice-to-have — useful signal for future refinement
6. Capture examples or anti-examples where they help judgment.
7. Write a new versioned evaluation document.

---

Document Structure

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

# [Feature Name] Evaluation

## Context
What this evaluation is trying to judge.

## Scenarios
### Scenario 1: [name]
- Why it matters
- Representative example

## Criteria
### Must-pass
- [criterion]

### Should-pass
- [criterion]

### Nice-to-have
- [criterion]

## Gaps and Backtracks
What could not be judged yet, and whether requirements clarification is needed.

## Premises
Assumptions this evaluation version depends on.

---

Rules

• Create a new versioned file instead of editing an old one in place.
• Evaluation is the judgment layer, not the implementation layer.
• If criteria depend on undefined premises, stop and send the work back toward requirements clarification.

---

Delivery

After saving the document:

"Evaluation document complete and saved to docs/evaluation/<filename>.md. Please review it before using it to drive a solution."