pal-e-docs

Issue Template

template-issue Template

active template
Project

Issue Template

Design Principle: Issue-as-Spec

Issues live in Forgejo. Period.
The Forgejo issue IS the complete agent-executable spec (Markdown). Plan phases link directly to Forgejo issues. There are no pal-e-docs issue notes — that layer is eliminated.
Layer Lives in Format Audience
Projects, Plans, Phases, SOPs pal-e-docs HTML Betty Sue
Issues (specs) Forgejo Markdown Dev agents
PRs, Code Forgejo repos Markdown / code Dev agents, QA
Traceability chain: Project → Plan → Phase → Forgejo Issue → PR. Betty Sue owns everything left of the arrow to Forgejo. Agents own everything right.

Forgejo Issue Template

How Betty Sue Tracks Issues

Betty Sue does NOT create pal-e-docs notes for issues. Instead:
  • All work items are typed Forgejo issues on a project board
  • Forgejo's own open/closed state tracks lifecycle — no need for issue,open / issue,resolved tags
  • Betty Sue creates the Forgejo issue, adds it to the board, spawns the agent when it reaches next_up

What Changed (2026-03-02)

  • Eliminated pal-e-docs issue notes entirely. Issues are Forgejo issues. No HTML tracker notes, no issue-* slugs, no issue,open tag lifecycle.
  • Plan phases link directly to Forgejo issues.
  • Added File Targets, Context, Test Expectations, Constraints sections to the Forgejo template.
  • Validated by dogfood: agent executed from Forgejo issue alone with ~100 token prompt (31K total, 2.7 min).