seed-packet-crud-fields

ARCHIVED

Simple Seed Organizer already has the core add/import/list/detail/edit/delete loop, but seed packet data is still shaped by a fixed set of hardcoded fields. The next product slice should make it clear which seed fields are canonical, which can be added or retired over time, and how gardeners record manual knowledge that is not printed on the packet, such as notes or personal annotations to planting instructions.

STAGES

  1. proposal08-14
  2. requirements08-14
  3. design08-14
  4. tasks08-14
  5. build—
  6. archived08-14

CAPABILITY

  • seed-packet-management8 requirements

OUTCOMES — 35 OF 36 DONE, AND NOT MAPPABLE TO A CAPABILITY

This change organises its tasks by workstream rather than as spec scenarios, so progress cannot be split per capability.

WHAT HAPPENED

  1. ARCHIVED

    proposal and specs and design and tasks and archive landed

    2026-08-14 · 1 pull request
    • #370chore(openspec): drain the change queue and collapse to one schema

History read from a manifest built at 2026-09-30 (09e7bcc).

1 pull request, found by commits touching the change folder