Lead issues with a user story; track cross-repo stories in strategy #22

Merged

vnprc merged 1 commit from agent/issue-writing-user-story into master

2026-07-16 16:40:36 +01:00

allod-agent commented

2026-07-16 16:38:56 +01:00

Member

Makes agents lead each issue with a plain-English user story — the operator-facing "So that I can ..." outcome — instead of the technical artifact. The old rule ("the title and opening sentence should name the first repo-scoped change") actively pushed the human goal out of the issue, so reading a single ticket didn't tell you what UX outcome it served.

Also adds the cross-issue rule: when a story spans issues or repos, its single home is allod/strategy — a dev-plans/ Goal for big arcs, else a tracking issue with a cross-repo - [ ] allod/<repo>#N task list — and each child leads with the same one-liner plus Part of allod/strategy#N. The canonical story stays in one place so it can't drift across tickets.

Why strategy and a task list, not a milestone/epic: Forgejo (14.0.4) has no native epic type; milestones and labels are per-repo; projects and issue dependencies aren't exposed to the forge CLI. A strategy tracking issue with markdown cross-references is the only cross-repo, agent-drivable option, and strategy already hosts cross-cutting issues.

Docs-only (R0): a convention change, no behavior or generated artifacts.

Makes agents lead each issue with a plain-English **user story** — the operator-facing "So that I can ..." outcome — instead of the technical artifact. The old rule ("the title and opening sentence should name the first repo-scoped change") actively pushed the human goal out of the issue, so reading a single ticket didn't tell you what UX outcome it served. Also adds the cross-issue rule: when a story spans issues or repos, its single home is `allod/strategy` — a `dev-plans/` Goal for big arcs, else a tracking issue with a cross-repo `- [ ] allod/<repo>#N` task list — and each child leads with the same one-liner plus `Part of allod/strategy#N`. The canonical story stays in one place so it can't drift across tickets. Why strategy and a task list, not a milestone/epic: Forgejo (14.0.4) has no native epic type; milestones and labels are per-repo; projects and issue dependencies aren't exposed to the `forge` CLI. A `strategy` tracking issue with markdown cross-references is the only cross-repo, agent-drivable option, and `strategy` already hosts cross-cutting issues. Docs-only (R0): a convention change, no behavior or generated artifacts.

allod-agent added 1 commit

2026-07-16 16:38:56 +01:00