/prd-to-goal

name: prd-to-goal
description: "Decomposes a PRD, issue, or spec into a copy-pasteable `/goal until ... abort-if ...` line. Use when running /goal against a spec, to reduce acceptance criteria to AND-joined boolean assertions."
argument-hint: "[prd-text | issue#N | path/to/spec.md]"
tags: [/goal, planning, prd, automation, cc-2.1.139]
version: 0.1.0
author: OrchestKit
license: MIT
compatibility: "Claude Code 2.1.220+ (uses GA `/goal` loop)."
user-invocable: true
complexity: low
context: inherit
persuasion-type: guidance
allowed-tools: [Read, Write, Bash, Grep, Agent]
metadata:
  category: planning
  milestone: M140
triggers:
  keywords: ["prd to goal", "goal from prd", "convert prd to goal", "/goal from issue", "decompose acceptance criteria"]
  examples:
    - "turn this PRD into a /goal line"
    - "what should my /goal until clause be for issue #1792"
    - "decompose this spec into observable assertions"
  anti-triggers: [implement, fix, commit, refactor, push]

/ork:prd-to-goal — PRD → /goal Decomposition

Converts a PRD / issue / spec into a single copy-pasteable `/goal` line. The hard part of `/goal` is not running it — it is writing an `until` clause that is *convergent* (terminates), *falsifiable* (testable boolean), and *observable* (the agent can actually check it without subjective judgement). This skill makes that decomposition reproducible.

1. When to use

**Use it when:**

• You have a written PRD, GitHub issue, or spec and want to run `/goal` against it.
• Past `/goal` runs drifted, looped, or burned tokens because the `until` clause was vague (`until tests pass`, `until done`, `until design is good`).
• You need to justify the abort budget — turns, tokens, no-progress threshold.

**Skip it when:**

• One-shot bug fix where the failing test *is* the acceptance criterion. Just run `/goal until pnpm test -- auth.spec.ts passes`.
• No written PRD exists. Run `/ork:write-prd` first — vibes do not decompose.
• The work is destructive or irreversible (DB migrations, mass file deletes). `/goal` retries; you do not want retries on `DROP TABLE`.

2. Inputs the skill accepts

| Input | How | |---|---| | Pasted PRD text | Provide as the argument, or paste into the chat after invoking. | | GitHub issue | `gh issue view <N> --json title,body,labels` — the skill reads `body`. | | Spec file | Path to a Markdown / text file; the skill `Read`s it. | | ADR / design doc | Same as spec file. |

3. The decomposition algorithm

1. **Extract acceptance criteria.** Pull every `MUST`, `SHOULD`, `Definition of Done`, `Acceptance Criteria`, and checkbox-style line. If the doc has none, stop and tell the user to run `/ork:write-prd` first — there is nothing to converge on. 2. **Map each criterion to an observable boolean.** Each criterion must reduce to a single shell-checkable assertion. Examples of observable state:

• `test -f path/to/file` (file exists)
• `pnpm test -- pattern passes` (test command exits 0)
• `gh pr view <N> --json state | jq -r .state == "MERGED"`
• `wc -l < src/auth.ts` returns a number within bound
• `pnpm lint` exits 0
• `curl -sf $URL` returns 2xx

3. **Reject non-observable criteria.** Drop or rewrite criteria that depend on subjective judgement (`code is clean`, `design feels right`, `users are happy`). Either find a proxy (`lint exits 0`, `Lighthouse score > 90`, `NPS survey ID exists`) or surface the criterion back to the user as out of scope for `/goal`. 4. **Compose the `until` clause.** AND-join the observable assertions in priority order — the cheapest, most likely-to-fail check first so the loop short-circuits early. Three to five assertions is the sweet spot; more than seven usually means the PRD is two PRDs. 5. **Compose the `abort-if` clause.** Pick a turn cap, token cap, and no-progress detector. Sensible defaults:

• Turns: `15` for a single feature, `30` for a refactor, `5` for a bug fix.
• Tokens: `100000` (1 USD-ish on Sonnet) for a feature, `30000` for a bug fix.
• No-progress: `3` turns with no file changes and no new test passing.

4. Output template

The skill emits exactly two lines, ready to paste:

/goal until <assertion_1> AND <assertion_2> AND <assertion_3>
/goal abort-if turns > <N> OR tokens > <T> OR no_progress_for_<K>_turns

No commentary, no markdown wrapper — the user copies the block straight into Claude Code.

Optional: rubric emission (`.claude/rubric.json`)

When the user wants graded feedback beyond pass/fail booleans, the skill MAY also emit `.claude/rubric.json` conforming to `ork-rubric/1.0` (schema: `${CLAUDE_PLUGIN_ROOT}/skills/shared/rubric.schema.json`), mapping each acceptance criterion to one dimension:

{
  "rubric": "ork-rubric/1.0",
  "skill": "prd-to-goal",
  "dimensions": [
    { "name": "regression_test_added", "weight": 0.4, "min_pass": 8, "min_blocker": 3 },
    { "name": "auth_suite_green",      "weight": 0.4, "min_pass": 10, "min_blocker": 5 },
    { "name": "lint_clean",            "weight": 0.2, "min_pass": 10, "min_blocker": 0 }
  ]
}

Scores are 0–10 (`min_pass` = soft floor, `min_blocker` = hard blocker regardless of composite); dimension weights MUST sum to 1.0 — see the schema for the full contract.

The file is deliberately **user-editable before the `/goal` run** — that is the point. Adjusting weights and `min_pass` thresholds is how the user injects judgement into the loop without rewriting assertions (rubric-as-environment-feedback, Lance Martin 2026-06-09). The post-timeout grader (§8) treats the rubric, if present, as the user's intent — senior to the literal assertion text.

5. Worked examples

Example A — Bug fix PRD

Input (issue body):

Title: Login fails on emails containing "+"
Acceptance Criteria:
- New regression test in tests/auth/test_login.py covers email with "+"
- The new test passes
- All existing auth tests still pass

Output:

/goal until test -f tests/auth/test_login.py AND pnpm test -- tests/auth/test_