Skip to content

Commit 823f27e

Browse files
jacoblewisauclaude
andcommitted
docs(goal): resolve slice-2 shapes (guided form + native sub-issues)
Record the maintainer's choices from the grounded research + prototype step: Project template is the guided 5-field GitHub Issue Form (A2); the roadmap uses native GitHub sub-issues (B2). Capture the sub-issue creation mechanism and the robustness fallback (create child, read its id, POST sub_issues, retry once, fall back to a task-list line on persistent failure), since gh cannot set a parent and the endpoint has reported flakiness. Grounded in GitHub primary docs (Issue Forms, sub-issues REST API, task lists, cli/cli#10298). Throwaway prototype deleted. Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
1 parent 94e8ae3 commit 823f27e

1 file changed

Lines changed: 29 additions & 0 deletions

File tree

‎goals/operator-as-non-coder.md‎

Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -356,6 +356,35 @@ with the prototype skill:
356356
These are resolved in a research-plus-prototype step before any planner code is
357357
written. Findings and the chosen shapes append here.
358358

359+
### Slice 2 shapes resolved (session 5, maintainer via prototype)
360+
361+
Grounded in GitHub primary docs (Issue Forms syntax; sub-issues REST API; task
362+
lists), then compared in a throwaway prototype. The maintainer chose, over the
363+
recommended low-risk defaults, the richer options:
364+
365+
- **Project template: A2, the guided GitHub Issue Form (YAML).** Five fields:
366+
what to build, who for, what it must do first, what must never go wrong
367+
(optional), and a "roughly how big" dropdown. Lives at
368+
`.github/ISSUE_TEMPLATE/project.yml`, auto-applies `ribo:project`, fields use
369+
`required` validation. The "what must never go wrong" field is a domain signal
370+
the planner triages first.
371+
- **Roadmap: B2, native GitHub sub-issues.** The parent Project Issue shows a
372+
sub-issue progress bar; children are real sub-issues.
373+
374+
Engineering note (inform-only, my call to make B2 robust): native sub-issues
375+
cannot be created with `gh issue create`, and the gh CLI cannot set a parent. The
376+
planner will create each child with `gh issue create`, read its integer id
377+
(`gh api repos/{o}/{r}/issues/{n} --jq .id`), then `POST
378+
/repos/{o}/{r}/issues/{parent}/sub_issues` with `sub_issue_id`. Because that
379+
endpoint has reported flakiness, the call retries once and, on persistent
380+
failure, falls back to appending a `- [ ] #n` task-list line to the parent so the
381+
parent-child link is never silently lost. A new structural invariant will assert
382+
the planner keeps both the sub-issue call and the task-list fallback.
383+
384+
Sources: GitHub Issue Forms syntax, REST API for sub-issues, Adding sub-issues,
385+
About task lists, and cli/cli#10298 (gh cannot set a parent). The prototype
386+
(`/tmp/ribosome-proto/planner-shapes.html`) has served its purpose and is deleted.
387+
359388
---
360389

361390
## Decisions (settled session 5, maintainer)

0 commit comments

Comments
 (0)