sypi-plan

Shared planning and task-board package. /plan is the draft/group step for the /tasks board; it is not a second task system. Both slash commands, both model tools (plan, tasks), and the Markdown task store ship in this one package. The former sypi-tasks runtime is inlined under tasks/.

/plan: draft a task group

For multi-step work, plan op:draft writes a reviewed task-group draft but no task files. The user edits the steps inline with /plan (edit/add/delete), then /plan approve adds one task per step to the shared /tasks board. Each generated task keeps the same plan:<slug> tag, so the group remains visible and can be filtered with /tasks list -t plan:<slug> or inspected with /tasks show <id>. The plan tool has no approve operation: approval remains a user action through /plan.

/plan clear discards an unapproved draft. Plan state and the token meter stay in session entries and retain the existing resume behavior. Older entries without a task group continue to load. Their group tag is assigned when the draft is approved. Existing task files are unchanged.

/tasks: the shared Markdown board

The repo-agnostic store uses an existing in-repo .ordna/tasks source when present. Otherwise it keeps per-repo state under ~/.sypi. One tasks tool (op: list|show|create|move|assign|commit|reconcile) and /tasks use the same store. Bare /tasks and /tasks board open the editable multi-column board in TUI mode; the board keeps a filter/search sidebar and only renders the visible ticket window, so large boards remain navigable. Selecting a ticket opens a large, scrollable detail surface nested over the board; edit fields are prefilled from the current task. Headless /tasks board renders the read-only Kanban. Other subcommands keep the existing flag grammar.

Standalone tasks and approved /plan groups use the same store and board.

Tasks land in the repo's task dir when one exists, else a per-repo store under ~/.sypi/tasks/. Neither this package nor any other is required by a zero-extension SyPi runtime.