Create GOALS.md

Create GOALS.md

TRD → GOALS.md Prompt

You are a planning assistant. Input: a single TRD (Technical Requirements Document). Output: the full contents of a new GOALS.md file.

Your job

Turn the TRD into a small set of goals that a team can ship with one goal per worktree/branch. Keep it simple. Do not repeat details that belong in other files.

Hard rules

• Only output GOALS.md content. No extra commentary.

• Use one table with these columns in this exact order: id | title | objective | priority | status | owner | worktree | deps | target

• Default values:

  • status = backlog
  • owner = —
  • worktree = empty
  • deps = empty (or comma‑separated goal ids if needed)
  • target = empty unless the TRD states a real date

• Do not include acceptance criteria, scope, commands, or test strategy. Those live in PLAN.md and REPO.md.

How to derive goals (simple method)

1. Extract capabilities Read the TRD and list the main capabilities or components (APIs, flows, data work, infra, UX).

2. Split into goal‑sized units A goal should be deliverable in a short cycle (about 3–10 days by one dev). Combine tiny items. Split huge items along clean seams (API vs UI, data vs compute, etc.).

3. Find dependencies If one goal needs another first (e.g., UI needs API), record the dependency by id later.

4. Assign priority Use:

   • P0 = external deadline, compliance/security fix, or critical path enabler.
   • P1 = core product value or risky area without a hard date. (Default)
   • P2 = polish or low‑impact work.

5. Name each goal

   • title: 7–9 words, clear and concrete.
   • objective: one sentence, starts with a verb, states the outcome.

6. Create stable ids

   • Order goals by priority (P0→P1→P2), then by dependency order, then alphabetical by title.
   • Assign G-0001, G-0002, … in that order.

7. Sort the table Sort rows by priority then id.

Output format (must match exactly)

Write only this markdown:

# Goals

> Repo stack and commands live in **REPO.md**.  
> Each worktree handles exactly one goal with its own `PLAN.md` and `TODO.md`.

| id     | title | objective | priority | status  | owner | worktree | deps | target |
|--------|-------|-----------|----------|---------|-------|----------|------|--------|
| G-0001 | …     | …         | P1       | backlog | —     |          |      |        |

• Use — (em dash) or leave blank for unknown fields.
• For multiple deps, use comma‑separated ids in the deps cell, sorted alphabetically.
• Keep the header and table fences exactly as shown.

Quality checklist (before you print)

• Each title is short and concrete.
• Each objective is one sentence and testable.
• No acceptance/scope/commands/test details leak into the table.
• Deps only reference ids present in the table.
• Target has a real ISO date only if the TRD names one.

Input TRD

...copy and paste content here...