pal-e-docs

Plan Template

template-plan Template

template deprecated
Project

Plan Template

DEPRECATED (2026-03-26) — Plans are replaced by kanban boards + architecture diagrams per convention-kanban-over-plans. Existing plan notes are preserved as historical artifacts. Do not create new plans. See template-ticket and sop-board-workflow for the current model.

Template

Phase → Forgejo Issue Flow

When a phase is ready to execute:
  • Betty Sue creates a Forgejo issue on the target repo using template-issue
  • Betty Sue records the issue number in the plan phase: Forgejo Issue: org/repo #N
  • Betty Sue spawns a dev agent with the minimal prompt (see agent-spawn-conventions)
  • Agent reads the Forgejo issue, writes code, creates PR
  • Betty Sue updates the phase with deliverables after merge
No pal-e-docs issue notes. The Forgejo issue IS the spec. The plan phase IS the tracker.

What Changed (2026-03-02)

  • Phases link directly to Forgejo issues — Forgejo Issue: org/repo #N replaces pal-e-docs issue note references
  • Phase → Forgejo Issue flow documented — the lifecycle from plan to PR
  • Removed "issue note slug" from phase requirements — no more issue-* notes in pal-e-docs
  • Added Repo field to phase template — makes it clear which repo the work targets

Previous Changes (2026-02-25)

  • Phases now require a slug: phase-{plan-date}-{n}-{short-description}
  • Phases now specify an owner: main session or agent type
  • Completed phases must list deliverables
  • Phase granularity rule added: phases must be independently deployable

Recursive Plan Structure

Plans link to each other via Previous Plan, Depends On, and Next Plan Seeds, creating a DAG (directed acyclic graph) of plans, not a linear chain.
Note: The previous convention of promoting phases to their own plans is retired by plan-2026-03-01-note-decomposition. Once note decomposition is implemented, phases become their own notes linked to a parent plan via parent_note_id and grow in place instead of being promoted. Until then, phases remain inline HTML sections within the parent plan.

Plan Lifecycle Tags

  • plan,active — currently being worked on
  • plan,deferred — blocked on a dependency
  • plan,completed — all phases done

Naming Convention

Slug: plan-YYYY-MM-DD-short-title
Tags: see Plan Lifecycle Tags above
Project: the primary project this plan advances

Phase Slug Convention

Slug: phase-{plan-date}-{n}-{short-description}
Example: phase-2026-02-25-1-agent-profiles
The plan date ties the phase to its parent plan. The number gives ordering.