tegwick
b8cd584c72
Housekeeping triggered by the Forgejo daily-todo-md-stale-review flag (the-custodian issue #5, 12 days stale). Reviewed: the plan was written 2025-12-17 and its dependency (issue-facade) was detached the same day (capabilities/DETACHED-issue-facade.yaml) and never re-integrated since -- only a repo-wide rename has touched it in 7 months. No workplan, roadmap topic, or other repo picked this up. Archived per this repo's own history/yymmdd-topic/ convention rather than promoted to a workplan nobody asked for; TODO.md reset to clean. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
22 lines
976 B
Markdown
22 lines
976 B
Markdown
# Todofile
|
|
|
|
This is a "to do next" file, particularly useful to keep the human and a coding assistant in sync.
|
|
|
|
The format is based on [Keep a Todofile V0.0.1](https://coulomb.social/open/KeepaTodofile).
|
|
|
|
The structure organizes **future tasks** by their impact, just as a changelog organizes past changes by their impact.
|
|
|
|
See roadmap/YYMMDD-ROADMAPTOPIC/ directories for planning information like concepts, workplans, etc...
|
|
|
|
***
|
|
|
|
## [Unreleased] - *Active Vibe-Coding State* 💡
|
|
|
|
This section is for tasks currently being discussed with or worked on by the coding assistant. These are the ephemeral, flow-of-thought tasks.
|
|
|
|
*(clean — 2026-07-20. Prior entry, "Extract Capability-Capability from
|
|
Issue-Facade," archived to
|
|
`history/260720-issue-facade-capability-extraction-paused/` after 7 months
|
|
with no forward motion and its dependency (`issue-facade`) detached the
|
|
same day it was written; see that directory's README for the full
|
|
rationale.)*
|