Create 'goal' issue type in roadmap

[jwildfire]

instead of goals living in markdown files save them as github issue with a new type = goal and a new template.

[obotclaw[bot]]

@jwildfire — this looks like it may reverse decision O2 in design #18 (§7), decided 2026-07-22: "Goal definitions live in obot.agent goals/" as markdown files (one per goal, YAML frontmatter over prose), specifically so they're versioned with the --auto machinery that consumes them (scripts/obot-auto) and always wait for your review via the scaffold-lane carve-out.

Before I write a requirement, three questions:

1. Is the intent here to supersede O2 — moving goal storage from obot.agent/goals/*.md to roadmap issues — or is this about a different, unrelated notion of "goal" (e.g. a lightweight tracking view that sits alongside the existing goal files rather than replacing them)?
2. If superseding O2: what's changed since 2026-07-22 that makes issues preferable to files (e.g. losing the frontmatter fields like anchors, backlog, grant_profile, status that --auto selection reads)?
3. Is "type = goal" meant as a GitHub-native issue type, or the same label + template pattern already used for requirement (per .github/ISSUE_TEMPLATE/requirement.yml)?

---

This was drafted by obot ideas-triage (Claude Code headless using Sonnet 5) — review by @jwildfire.

[jwildfire]

1. Yes. it supercedes 02.
2. Nothing changed. Just iteration.
3. Yes. new issue type with new template. (not same as requirement). goal issues will typically serve as parents for requirement issues.

[jwildfire]

🔔 Triage nudge - see response to comments above

[obotclaw[bot]]

Promoted → #71 — Requirement: goal issues (goals move from obot.agent files to hub issues).
Your three answers are baked in: it supersedes #18 O2 outright; goal issues typically parent requirements (via GitHub sub-issue links, which also resolves #53's open question); and the goal template is distinct from the requirement template.
One platform wrinkle handled in the issue: GitHub-native custom issue types are org-only — this user-owned repo cannot create them — so "type = goal" lands as a goal label + dedicated issue form unless the hub ever moves to an org.
The requirement also carries the O2 machinery across: migrating goals/charts.md / goals/app.md, switching scripts/obot-auto + session-init --auto to read goal issues, and a design decision on how the "goal edits wait for @jwildfire" carve-out survives the move.
Two pilot goal issues are already live from this sweep: #72 (keynote deck, from #52) and #73 (autonomy, from #54).
Closing as resolved.

---

This comment was drafted by Claude Code using Fable 5 and reviewed by @jwildfire